The RPM program also does extremely frequent fsync()/fdatasync() calls for the same "stupid"
reason. Just as Firefox, RPM should work on a non-sync copy of it's database and only sync it
once (at the end of a transaction) before renaming the copy over the original db.
Btw, for people who want to know where their system has such latencies.. the latencytop
program (www.latencytop.org) shows this and other bottlenecks right away. Linux is doing
rather poorly in some of these things, even when you ignore the "ext3 has a bad fsync, use
btrfs instead" problem ;-)