something I definitely want to do is: some side-by-side comparisons of 3.0.X to 3.2.X for speed and memory footprint.
We used the following test cases: * normal system (~1200 pkgs) * empty update (no updates) * small update (3-5 updates) * big update (150-200 updates) * dist upgrade to next F(C) release * install into chroot * normal install (1200 pkgs) - use groups, not a pkglist * full install (7500 pkgs) * erase glibc These cover most of the runtime behavior.
if for no other reason that to prove that we've done _something_ in all these changes. :)
I doubt that this will stay the only reason. Improving is difficult without measurement. Without testing the big cases quadratic, cubic or worse runtime behavior stays undiscovered.
Florian _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
