Bug 462086

Summary: yum is much slower for _many_ excludes
Product: Red Hat Enterprise Linux 5 Reporter: James Antill <james.antill>
Component: yumAssignee: James Antill <james.antill>
Status: CLOSED ERRATA QA Contact: Jan Hutaƙ <jhutar>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: jhutar, syeghiay
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-20 16:44:20 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description James Antill 2008-09-12 11:02:49 EDT
Description of problem:
 The 3.2.19 we have as an errata candidate for RHEL-5.3 has the following edge case bug we've just fixed upstream:


...the problem is that yum will always do some queries via. SQL now, however in some cases SQLite has performance problems. The bug above is for OLPC which is creating exclude lists with 2,200 packages in them, however:

time yum list $(perl -e 'print "python-urlgrabber " x 2200')

...will also hit the same problem.
 The speed difference is between ~2.5 seconds for a full repo. load, and upto 5 minutes for the above 2,200 package names. The fix isn't that complicated, so is viable.
 It's also worth noting that the speed drop is basically linear with the package list size, so if people are normally only doing 100-200 packages it'll only be a couple of seconds slower you.
Comment 1 RHEL Product and Program Management 2008-09-12 11:22:29 EDT
This bugzilla has Keywords: Regression.  

Since no regressions are allowed between releases, 
it is also being proposed as a blocker for this release.  

Please resolve ASAP.
Comment 8 errata-xmlrpc 2009-01-20 16:44:20 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.