Phoronix: 10-Way Linux File-System Comparison On Linux 3.10
On the latest Linux 3.10 stable kernel we have taken ten common Linux file-systems and generated an interesting performance comparisons. The Linux file-systems being tested in this article include XFS, Btrfs, EXT2, EXT3, EXT4, ReiserFS, Reiser4, JFS, F2FS, and ZFS.
http://www.phoronix.com/vr.php?view=19019
Announcement
Collapse
No announcement yet.
10-Way Linux File-System Comparison On Linux 3.10
Collapse
X
-
10-Way Linux File-System Comparison On Linux 3.10
Tags: None
-
What is the ultimate filesystem?Last edited by mazenmardini; 08-12-2013, 11:35 PM.
Leave a comment:
-
Efficient for Semi-Static Files, Numbers?
Originally posted by jwilliams View PostIncorrect. relatime only updates the access time if it is earlier than the last mtime/ctime. For example, with relatime, if a file is modified and then read, there will be a write to update the access time. If the file is read again, there will be no more writes to update the access time (until the file is modified again).
Leave a comment:
-
Originally posted by Artemis3 View PostAny time you read ANYTHING, a write must occur. Relatime delays the writes so they occur more efficiently, but they still occur.
Leave a comment:
-
Thanks, but...
Originally posted by Artemis3 View PostThink of it.
Any time you read ANYTHING, a write must occur. Relatime delays the writes so they occur more efficiently, but they still occur.
This is why i always use noatime. Almost nothing (mutt?) needs to know when was the last time a file was read, and the performance loss is not neglible, not to mention adding wear to flash media.
Leave a comment:
-
Use noatime instead of relatime
Think of it.
Any time you read ANYTHING, a write must occur. Relatime delays the writes so they occur more efficiently, but they still occur.
This is why i always use noatime. Almost nothing (mutt?) needs to know when was the last time a file was read, and the performance loss is not neglible, not to mention adding wear to flash media.
Leave a comment:
-
Great that JFS appears in a test
Over the years I've become pretty fond of JFS, which has never let me down, so it's great to see it included in this test. I wish Phoronix would include it in the other filesystem tests run from time to time. It may not be the latest thing, but it's solid, and always appears right up there in comparison tests like this. It's a pity that RedHat (and Fedora) SuSE (and OpenSuSE) make it difficult-to-impossible to install from scratch using JFS, but at least Debian has retained it as an option.
I find JFS great on KVM guests, especially with the noop scheduler.
While XFS is good too, especially for larger files, I was responsible for systems during the dreaded file corruption days if a filesystem wasn't shut down cleanly, now a forgotten episode, but that little sense of mistrust still remains long after the issue was resolved. I also have horrible memories of piecing together an EXT4 system from the lost+found folder, and lost an entire resier3 filesystem once, on a system running on another continent!
JFS has been great on lightweight systems too. I run one server at an off-grid location, where power consumption is a significant issue, not just an ideal. JFS is known to be frugal on processor demand, and squeezes good capacity from small disks too.
Any chance of Phoronix repeating that seminal 2007 file system comparison test done on Debian?
Leave a comment:
-
Most (all?) modern SSDs do compression themselves in hardware. Adding a software compression option therefore should not only cause performance decreases, but give also no advantages in used space. I would disable that on SSDs.
Leave a comment:
Leave a comment: