Btrfs Is Not Yet the Performance King 117
Ashmash writes "Benchmarks of the Btrfs filesystem have been published by Phoronix that compare it to the XFS, EXT3, and EXT4 file-systems. In the end they conclude that this next-generation Linux filesystem is not yet the performance king. In a great number of the tests, the EXT4 filesystem that was designed to be an interim step to Btrfs actually performs much better than the unstable Btrfs, albeit Btrfs still has more advanced features. Fedora 11 even took longer to boot when using Btrfs than EXT3 or EXT4."
Stability, reliability (Score:5, Insightful)
I don't care which filesystem is fastest. Kcryptd is the bottleneck on my system, so it really doesn't matter how fast the filessytem is. I want to know which filesystem is the most robust. What filesystem is least likely to lose data?
How is this news? (Score:4, Insightful)
Numbers for mysql performance on BTRFS? (Score:3, Insightful)
Btrfs is mainly created for the Oracle client that doesn't want to use "raw device". It's to improve performance reading/writing large files with high concurrency. So it have to be fast on concurrent request.
What should be looked is :
how mysql perform on BTRFS
how postgres perform on BTRFS
how firebird perform on BTRFS
As there is no magical solution, btrfs is no exception. It's not a general usage FS as is ext (imho). On the desktop, xfs will be the way to go. Performance-wise it's obviously not so great (I do realise that it's still in development and this might change in the future), and the features it delivers are not very interesting as well imho, except maybe for the online defragmentation thingy. But I'm not an enterprise user whis is what this fs aims at I assume.
Still I appreciate the work. Let's hope it doesn't get axed now that Oracle owns Sun and thus already has ZFS.
cheers
=Smidge=
Re:Stability, reliability (Score:2, Insightful)
With file systems, speed and data integrity are trade-offs.
Not at all. ZFS is a perfect example. Not only is it faster than any Linux file system, but also far more flexible, reliable and far far less likely to lose your data.
Re:Stability, reliability (Score:2, Insightful)
There is always a trade off between performance, correctness/robustness, and features.
Pick 2, and don't complain when a 99.99999% guarantee of no data loss is dog slow compared to a filesystem that offers minimal protection against (meta) data loss.
several useless metrics (Score:3, Insightful)
not sure why phoronix decided to include several test cases which are clearly bottlenecked by something other than the filesystem. Obviously, all 4 filesystems are gonna score the same.
try again (Score:1, Insightful)
with linus ranting against ext4 i expected to find 'ordered' (mount option to make ext4 acceptable) in the f****** article at least once, but didn't.
so, please guys: do yourself a favour and do the benchmark again! benchmarking ram against platters ain't fair!
ZFS? (Score:2, Insightful)
I didn't RTFA but why no mention of ZFS?
Re:several useless metrics (Score:3, Insightful)
Because Phoronix does really crappy pointless benchmarks all the time. Occasionally they sucker me into reading them and I always wish I hadn't
Re:Stability, reliability (Score:4, Insightful)
Re:Stability, reliability (Score:5, Insightful)
You're right, Sun had no idea their new license would be incompatible with Linux because they wanted to be compatible instead of doing the slimy thing and trying to make it be a selling point over using Linux, which everyone was doing. Alas. for them RMS and Linus travelled back in time and created/used the GPL just to thwart poor Sun.
Re:ZFS? (Score:2, Insightful)
The short version is that ZFS isn't available for linux, and this is a linux FS benchmark on a linux specific site.
You could run the same benchmark on OpenSolaris vs Linux on the same hardware, but this wouldn't be particularly meaningful: different storage stack, vfs, etc. Even if the benchmark convinced someone that ZFS is better, they couldn't switch to it, because again, there is no linux port.
You could benchmark the userspace ZFS on Fuse driver, but this is meaningless because the Fuse ZFS implementation is useless (slow + unstable) and everyone knows it.