https://bugzilla.novell.com/show_bug.cgi?id=897353 https://bugzilla.novell.com/show_bug.cgi?id=897353#c1 Bernhard Wiedemann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann@suse.com, | |jengelh@inai.de, | |rhafer@suse.com AssignedTo|bnc-team-screening@forge.pr |mls@suse.com |ovo.novell.com | --- Comment #1 from Bernhard Wiedemann 2014-09-19 08:49:53 CEST --- reproduced it with rpm # echo 3 > /proc/sys/vm/drop_caches ; time rpm -qa > /dev/null real 0m6.740s user 0m1.120s sys 0m0.252s # echo 3 > /proc/sys/vm/drop_caches ; time (cat /var/lib/rpm/* > /dev/null ; rpm -qa > /dev/null ) cat: /var/lib/rpm/alternatives: Is a directory real 0m3.781s user 0m0.672s sys 0m0.180s # time rpm -qa > /dev/null real 0m0.730s user 0m0.704s sys 0m0.024s -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=897353 https://bugzilla.novell.com/show_bug.cgi?id=897353#c3 --- Comment #3 from Claudio Freire 2014-09-19 16:24:19 UTC --- Don't be so quick at dismissing this. Sure, from Bernard's reproduction, it looks like a pointless thing. I'm not sure which hardware and setup he has, he probably has an SSD. For those without SSDs, this is a lot worse. Here, I've got a laptop with a rotating 5400RPM hard drive, and 13.1. Nothing wierd. There, I get: ~> echo 3 | sudo tee /proc/sys/vm/drop_caches ; time rpm -qa > /dev/null root's password: 3 real 0m45.919s user 0m1.990s sys 0m0.573s

echo 3 | sudo tee /proc/sys/vm/drop_caches ; time ( cat /var/lib/rpm/Packages > /dev/null ; rpm -qa > /dev/null ) 3

real 0m7.481s user 0m1.127s sys 0m0.286s So the difference is 6-fold. Second, this was brought up in the context of etckeeper, which is something that's done during package installation and causes real trouble, see: http://lists.opensuse.org/opensuse-factory/2014-09/msg00223.html Finally, even if you don't care about etckeeper, this is a performance bug from the POV of a bsddb3 user. A sequential scan is supposed to be sequential physically as well, and it should be fixable (the data structure should support it). So, you could do one or more of the following: a) Report it upstream (bsddb3) b) Report it upstream (rpm, they can implement the fadvise workaround, or switch to another bsddb implementation that doesn't have this issue) c) or work around it in everything that does package management -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.