Greg Thomas wrote:
I was getting really slow installs and erases with RPM so I figured I'd try to understand why. My RPM databases were running anywhere from 16KB for conflictsindex.rpm to 29MB for packages.rpm to 43MB for requiredby.rpm. This is with SuSE's rpm-3.0.3-34. And this was a system that was installed fresh at 6.2 and upgraded to 6.3.
I checked Maximum RPM on-line to see if there were any database optimizations available. The only one was --rebuildb and the documentation states that it is mostly for rebuilding corrupt databases. It goes on to state that it really isn't necessary to run --rebuilddb to reduce the size of the databases since RPM fills in empty spaces. Well, I decided to give it a shot anyway.
After rpm --rebuilddb the above databases were 16KB, 18MB, and 2.8MB! Requiredby.rpm is now less than 1/10th the size!
The result is that a simple install that was taking 20 to 40 seconds is only taking 3-4 seconds. Not to mention that I freed up a lot of space on my 172MB /var paritition!
Just thought you all would like to know.
Later, Greg
Thanks Greg I just duplicated this my fresh 6.3 install from A couple of months ago, and I had been blaming Yast for slow upgrades. Mike -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/