> > it's the depresolution using addInstall('a') modes.
> >
> > It's not going to be used in the future but changing the depresolution
> > mechanism in yum 2.0.x now doesn't seem to be the best use of time.
>
> I guess it depends on how significant a problem it is then. For me, it's
> enough that I want to fix it.
it's not a trivial amount of work.
> > in your particular case I'm betting you have a bunch of kernels
> > installed. It's a well known situation that yum and rpm get very very
> > large when doing updates/installs with lots of kernels installed.
>
> Yup. I've been doing some more tests and can see that it's definately
> related to the number of kernels installed.
>
> However, it's still an insane amount of memory usage with a small number
> of kernels installed.
how many repositories and how many total packages across all of those
repositories do you have? I'm betting it's a huge number.
-sv
