I did a related benchmark on a Debian unstable system (with dpkg 1.15.8.5 and linux-image-2.6.35-trunk-amd64) and an ext3/4 file system. Here were the results:
This affects my ext3/4 filesystem (ext3 mounted with the ext4 driver, but none of the advanced ext4 features enabled) as well. Iin a cowbuilder chroot (with all of the packages pre-cached by apt-cacher-ng):
# time eatmydata apt-get install –no-install-recommends openoffice.org
0 upgraded, 142 newly installed, 0 to remove and 0 not upgraded.
…
real 0m57.682s
user 0m37.030s
sys 0m7.220s
# time apt-get install –no-install-recommends openoffice.org
0 upgraded, 142 newly installed, 0 to remove and 0 not upgraded.
…
real 3m17.158s
user 0m37.186s
sys 0m11.057s
Over three times as long. So maybe you're getting a double hit with btrfs, but the first hit that dpkg is giving you on *any* filesystem is pretty bad to begin with.
I did a related benchmark on a Debian unstable system (with dpkg 1.15.8.5 and linux-image- 2.6.35- trunk-amd64) and an ext3/4 file system. Here were the results:
This affects my ext3/4 filesystem (ext3 mounted with the ext4 driver, but none of the advanced ext4 features enabled) as well. Iin a cowbuilder chroot (with all of the packages pre-cached by apt-cacher-ng):
# time eatmydata apt-get install –no-install- recommends openoffice.org
0 upgraded, 142 newly installed, 0 to remove and 0 not upgraded.
…
real 0m57.682s
user 0m37.030s
sys 0m7.220s
# time apt-get install –no-install- recommends openoffice.org
0 upgraded, 142 newly installed, 0 to remove and 0 not upgraded.
…
real 3m17.158s
user 0m37.186s
sys 0m11.057s
Over three times as long. So maybe you're getting a double hit with btrfs, but the first hit that dpkg is giving you on *any* filesystem is pretty bad to begin with.