Today I was reading about btrfs and as never used it before I thought in giving it a try.
On my laptop I have a ssd with 256GB, there I created 2 LVM2 volumes to use and test btrfs.
It’s not the ideal solution because there’s a LVM layer but I’m not in the mood for backup,erasing,installing,erasing and installing. So the tests I’m going to do are just on the FS itself, not on all the layers that btrfs supports. A good thing in using a ssd card is that the access time is equal for all the block device and the data position on the block device is not accountable, so this is a very good opportunity to have measurements both on ext4 and btrfs.
Here’s the benchmark architecture, tools and setup:
Linux MartiniMan-LAP 2.6.38-31-desktop #1 SMP PREEMPT 2011-04-06 09:01:38 +0200 x86_64 x86_64 x86_64 GNU/Linux
LVM lv creation command:
lvcreate -L 20G -n TestingBTRfs /dev/mapper/system lvcreate -L 20G -n TestingExt4fs /dev/mapper/system
LVM lvdisplay output:
--- Logical volume --- LV Name /dev/system/TestingBTRfs VG Name system LV UUID zBYf0d-metk-VC9U-YkjE-z1Ts-NMLb-HzYmrJ LV Write Access read/write LV Status available LV Size 20.00 GiB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:3 --- Logical volume --- LV Name /dev/system/TestingExt4fs VG Name system LV UUID FJEfiv-Hs9W-zGuV-sJIo-3INN-gh52-YgmsVl LV Write Access read/write LV Status available LV Size 20.00 GiB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:4
FS creation command:
mkfs.ext4 /dev/system/TestingExt4fs mkfs.btrfs /dev/system/TestingBTRfs
model name : Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz
Device Model: SAMSUNG MMDOE56G5MXP-0VB
Mount command (as you can see I didn’t do any optimizations, noatime, etc):
/dev/mapper/system-TestingBTRfs on /mnt/btrf type btrfs (rw) /dev/mapper/system-TestingExt4fs on /mnt/ext4 type ext4 (rw)
'Iozone' Filesystem Benchmark Program Version $Revision: 3.373 $ Compiled for 64 bit mode.
Command line for the tests:
Command line used:
./iozone -Ra -r4k -r8k -r16k -r32k -r64k -r128 -r1024 -r4096k -r16384k -s1g
This command was used in the btrfs and the ext4 volumes.
The options mean:
office compatible format.
-a auto test
-r the record size (you can see I used several (4k,8k…))
-s size of test file (I used 1GB)
Here’s the test results:
And the charts (The scale is logarithmic):
(you may download the data here: [download id=”1″])
As you can see on the charts for sequential reading/writing there’s a performance gain in BTRfs with the smaller record sizes but the inverse is also true, EXT4 has more performance on larger record sizes.
If you look to the random data access while reading or writing you’ll see that EXT4 is far faster that BTRfs, and this is according to my daily usage pattern would be 70% of the access to my hard drive. To be sincere I’m a bit surprised on such a difference. I know I didn’t tune any of the file systems and the purpose of this benchmark is not having to, just playing with the defaults as most of the installations out there.
Another conclusion that is really simple to understand is that bigger record sizes mean best performance.
For now I think I’ll stick to EXT4 and LVM, who knows if I’ll sometime soon I’ll change to BTRFS, I’ll let it grow and advise you to do the same.