Bug 757752 - Performance problems after uploading manifest
Summary: Performance problems after uploading manifest
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: API
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: Unspecified
Assignee: Miroslav Suchý
QA Contact: Jeff Weiss
URL:
Whiteboard:
Depends On: 747336
Blocks: katello-blockers
TreeView+ depends on / blocked
 
Reported: 2011-11-28 15:48 UTC by Jeff Weiss
Modified: 2019-09-25 21:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 18:11:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jeff Weiss 2011-11-28 15:48:48 UTC
Description of problem:
This bug is a tracker for using the new bulk repo query API in pulp (mark this MODIFIED when katello supports this api).  For more details see the dependent bug

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Lukas Zapletal 2011-12-08 16:05:13 UTC
Dep ON_QA. Please reopen when necessary.

Comment 2 Jeff Weiss 2011-12-08 22:23:38 UTC
Katello still creating repos one at a time, slows to a crawl for at least 15 minutes.  During that time all pages take way too long to load (like 3 minutes).

katello-0.1.135-1.git.0.668aa1d.el6.x86_64

Comment 3 Jeff Weiss 2011-12-08 22:26:21 UTC
I believe this bug is only fixed when katello uses the new pulp API that does batch operations.

Comment 5 RHEL Program Management 2012-02-23 10:05:01 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.

Comment 6 Miroslav Suchý 2012-08-22 08:31:38 UTC
Taking.
I belive this fix is addressed in current upstream and will be fixed in next version of CFSE, where we will be rebasing on current upstream.

Comment 8 Mike McCune 2012-09-13 15:17:21 UTC
moving to 2.0 since we didn't really make any inherent performance fixes for imports during 1.1

Comment 9 Mike McCune 2013-09-19 18:11:27 UTC
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.


Note You need to log in before you can comment on or make changes to this bug.