On Wed, 2008-02-27 at 23:52 -0500, seth vidal wrote: > 5. outputting more stats information about how long certain processes > take in a little more obvious way. IE: setup repos, setup rpmdb, setup > package sacks, setup update lists, depsolve, transaction test, > transaction run w/ simple -d 3 outputs so we can see where people are > seeing sluggishness.
okay I did a simple little patch for this one: I'll probably apply it: http://skvidal.fedorapeople.org/patches/yum-time-outputs.patch if you run with -d3 or -v you can grep easily to see how long certain bits are taking like: echo n | ./yummain.py -v install koffice-suite | grep 'time:' Config time: 0.283 - reading in config + .repo files rpmdb time: 0.000 - opening rpmdb/setting up ts pkgsack time: 0.422 - setup package sacks up:Obs Init time: 0.921 - call self.pkgsack.returnObsoletes(newest=True) up:simple updates time: 0.411 - simple updates up:obs time: 0.017 - obsoletes up:condense time: 0.000 - condense the updates updates time: 1.662 - total updates Depsolve time: 2.802 - total depsolve There are a few more, rpm check debug time, transaction test time and transaction time. it's clearly not perfect but it is does help spot obvious problems like returnObsoletes(newest=True) there. -sv _______________________________________________ Yum-devel mailing list [email protected] https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
