On Thu, 2004-12-30 at 22:50 -0800, Jamie Zawinski wrote:
Sean Middleditch wrote:
>
> The problem you're perceiving (slow operation as yum starts up) isn't at
> all due to lack of caching, but perhaps very inefficient handling of the
> cache - a lot of data has to be parsed and such, when it could perhaps
> be stored in a more ready-to-process format.
It takes *nearly a minute* to do that! I'm on a 2GHz machine.
If it's not hitting the net, what's it doing, raytracing?
That or maybe an embedded SETI@home client...?
It only takes a handful of seconds on my machine, which is only 1.5ghz.
Yum is *very* RAM intensive, so if you're low there, that might be the
slow down...?