fedup performance

Alex G. mr.nuke.me at gmail.com
Wed Jul 3 05:25:19 UTC 2013


On 07/03/2013 12:15 AM, Adam Williamson wrote:
> On 2013-07-02 21:42, Alex G. wrote:
>> On 07/02/2013 08:28 PM, Neal Becker wrote:
>>> Not d/l speed related.  I just want to share.  I update a very fast 8
>>> core
>>> server, with a conventional disk drive.  Took 2-3 hours, not
>>> including d/l.
>>>
>>> I update my laptop which has an ssd (and MORE packages).  Took 10-15
>>> minutes.
>>>
>> I think this might simply have to do with rpm running ldconfig (a very
>> disk IO expensive operation) for a large number of packages. I'm not
>> sure yum/rpm has deferred ldconfig processing.
> 
> rpm has the concept of %posttrans . Stuff in %posttrans is run after
> *the entire transaction* has completed, not after *the specific package
> install* has completed.
> 
> However, I think we can't put ldconfig in %posttrans, because what
> happens if a package installed later relies on the ldconfig being
> correct for a package installed earlier in the same transaction?
> 
aptitude has something called "deferred ldconfig processing", and
annoyingly, aptitude updates faster than yum. I've always wondered how
yum/rpm can be smartized to speed things up this way. But this
discussion is for a brighter day.

>> DISCLAIMER: I may be very wrong. Please don't quote me on this.
> 
> Seconded =)
My name is Alexandru Gagniuc, and I approve this message. :)

Alex


More information about the devel mailing list