-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-ID:
The 'sample' file is 100B size, with random content, and the test is run on a virtual machine (vmplayer) with 13.1 RC1
These were the results:
time (real/user/sys) number used free of files space space
reiserfs 62m32s/ 11m24s/ 35m27s 1000000 286M 1,8G ext4 8m14s/1m28/4m41s 141736 541M 1,3G (fails) xfs 30m19s/ 5m25/ 17m7 488254 2,0G 104K btrfs can not test (1)
Fill test - 10⁶ files, 100 bytes each. number | time (real/user/sys) | rm files time | used free % of files | | (real/user/sys) | space space reiserfs 1000000 | 62m18.341s/11m16.432s/35m44.060s | 0m30.594s/0m0.583s/0m27.837s | 259M 1,8G 13% ext4 131635 | 8m05.024s/01m26.484s/04m37.876s | 0m02.143s/0m0.154s/0m01.824s | 546M 1,3G 30% - failed: spent inodes. ext3 131635 | 8m08.570s/01m27.086s/04m40.344s | 0m01.994s/0m0.159s/0m01.665s | 522M 1,3G 29% - failed: spent inodes. xfs 478941 | 30m23.573s/05m20.020s/17m15.349s | 0m23.925s/0m0.481s/0m20.670s | 2,0G 20K 100% - failed btrfs 1000000 | 67m1.486s/ 11m44.258s/38m4.694s | 6m06.872s/0m0.489s/1m14.960s | 1,3G 566M 70% However, btrfs breaks on this test. After removal of the files, it is still full, without snapshots: Filesystem Size Used Avail Use% Mounted on /dev/sdb7 2,0G 648K 7,5M 8% /data/btrfs ***** btrfsck repairs nothing. There is a bugzilla on this. Both reiserfs and btrfs are the winners in number of small files they allow, but btrfs is simply not reliable, it breaks. Both ext3 and ext4 fail to allow that big number of files. xfs also fails, but it is better than ext3/4. Speed test - done with only 10000 files of 100 bytes each so that all filesystems can cope: time (real/user/sys) | | used free % cp files | rm files |space space usd reiserfs 6m05.288s/1m4.242s/3m29.046s | 0m1.933s/0m0.104s/0m1.775s | 55M 2,0G 3% ext3 6m06.564s/1m3.989s/3m30.341s | 0m1.457s/0m0.138s/0m1.219s | 397M 1,5G 22% ext4 6m09.012s/1m5.431s/3m30.416s | 0m1.518s/0m0.110s/0m1.327s | 422M 1,4G 23% xfs 6m11.045s/1m4.769s/3m31.739s | 0m3.998s/0m0.127s/0m3.464s | 632M 1,4G 31% btrfs 6m02.617s/1m4.548s/3m27.906s | 0m2.912s/0m0.113s/0m2.648s | 119M 1,8G 7% All filesystems are equally fast in virtual hardware. Interestingly, xfs is slow removing many files (rm -rf $WHERE/), and btrfs is slow too, but faster. Possibly the timing results would be different in real hardware. Speed test - done with 2000 files of 10000 bytes each so that all filesystems can cope: time (real/user/sys) | used | free % cp files | rm files space | space usd reiserfs 1m12.859s/0m12.199s/0m41.629s 0m0.500s/0m0.014s/0m0.470s 270M 1,8G 14% ext3 1m12.677s/0m12.330s/0m41.809s 0m0.295s/0m0.022s/0m0.260s 238M 1,6G ext4 1m12.288s/0m12.652s/0m41.277s 0m0.318s/0m0.020s/0m0.286s 247M 1,6G 14% xfs 1m12.528s/0m12.653s/0m41.425s 0m0.765s/0m0.024s/0m0.689s 337M 1,7G 17% btrfs 1m11.970s/0m12.462s/0m41.382s 0m0.637s/0m0.020s/0m0.585s 221M 1,6G 13% I'll post other set of results done on real hardware. The virtual machine simply does not have enough CPU power, and the virtual disk is also slow. - -- Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJs530ACgkQtTMYHG2NR9WP8gCeO8uwMlqN7mipONip3tYJNcFF 2T0AnjQk8KO2f4l8Aq1uKEMGmrrezRnf =+ji9 -----END PGP SIGNATURE-----