On 02/14/2018 10:14 PM, Matthew Miller wrote:
I'd be super-interested in benchmarks comparing before and after
install times. I guess since the plan is to do this _after_ the mass
rebuild, we'll need to wait until after the *next* rebuild to see how
much impact this has.
Many years ago, I remember a Fedora upgrade (from version 4 to 5, I think)
on a SATA disk on a Dual CPU PowerMac G5 (great machine at that time).
The upgrade was progressing incredibly slow, and I was able to discover
that every lib package upgrade was triggering ldconfig and spending a lot of time.
So I renamed /sbin/ldconfig away (replaced with a stub or something), and speed
went way up. After the RPM upgrade phase, I restored ldconfig and run it manually.
When I proposed this kind of optimization in some mailing list (maybe this one?!),
I was answered that my method was not entirely safe because there could have been
problems for some rpm scripts calling libraries that had been just upgraded
(e.g. perl libraries) without a proper ldconfig refresh.
Was that a valid consideration? Has something changed on that front?
I was convinced that ldconfig was a sort of cache, not critical to actually
find libraries.
Regards.
--
Roberto Ragusa mail at robertoragusa.it