Originally posted by energyman
View Post
Announcement
Collapse
No announcement yet.
Linux 3.3 Kernel: Btrfs vs. EXT4
Collapse
X
-
-
Originally posted by fackamato View PostSince SSDs are tiny, I don't mind having compression enabled sometimes saving ~50% of space on a filesystem, with non-noticeable performance impact.
Leave a comment:
-
oh look, btrfs a lot faster than ext4 in a real world example.
Leave a comment:
-
Originally posted by AnonymousCoward View PostExcept that on a Sandforce SSD, when it does save noticeable amounts of space, it will have a noticeable performance impact.
100GB SF SSD, 1 single btrfs partition. So let's say ~95GB or so available to the user. If the user writes 95GB of iso files with no compression, the performance while writing will be good and he'll use the entire filesystem.
If he choses to mount the filesystem with some compression option (lzo or something as fast) then the write performance will suffer a bit (at ~ 500MB/s, who cares? It's a tradeoff I guess.), but the user will still have some free space on the file system, depending on how good lzo is at compressing these ISO images. Therefore, the user can store more data than the SSD is physically capable of.
Leave a comment:
-
Originally posted by fackamato View PostSince SSDs are tiny, I don't mind having compression enabled sometimes saving ~50% of space on a filesystem, with non-noticeable performance impact.
Leave a comment:
-
Originally posted by liam View PostIt's not visible to the file system, but if you have a SF controller you shouldn't run filesystem level compression b/c it's superfluous. At best you may save a bit of space, but it will, in all cases, slow down your ops.
What is it I'm missing?
Leave a comment:
-
Originally posted by fackamato View Post.. which is not visible to the filesystem, so compression still matters a lot.
Leave a comment:
-
Originally posted by mayankleoboy1 View PostI am disappointed by the stock performance of BTRFS. It has been said to be the next standard linux file system and it cant compete with ext4.
Is transparent compression the only saving grace of BTRFS?
The principal advantage that Ext4 is going to have is that some of it's code is decades old and has hundred's of man-hours poured into it's development. It is very mature and there is very little that is going to surprise you with it and best practices are well established and widely known.
Btrfs on the other hand is going to require years of in-field usage and wide scale deployment before it can compete with Ext4 with that. But what Btrfs offers is significantly enhanced ability to manage data and from a administrative standpoint this is going to be invaluable once people learn to take advantage of it.
.. which is not visible to the filesystem, so compression still matters a lot.
Most data people care about performance nowadays is already heavily compressed. If you care about, say, your ability to use Linux to manage multimedia files then compression is utterly irrelevant on the file system level and on the controller level. They use format-specific compression techniques and the chances of file system compression helping out is _NONE_AT_ALL_.
Now if you are dealing with thousands of plain text files ranging in size from 2MB to multiple GBs then compression is something that is probably going to matter a lot to you. That is, of course, you are not already using gzip or whatever to compress your data.
Leave a comment:
-
Any upcoming benchmark with transparent FS compression on Phoronix ?
OpenBenchmarking.org, Phoronix Test Suite, Linux benchmarking, automated benchmarking, benchmarking results, benchmarking repository, open source benchmarking, benchmarking test profiles
It would be nice to compare http://openbenchmarking.org/result/1...AR-BTRFSLZ4124 with http://openbenchmarking.org/result/1...BY-LINUX33BT16 and others in a single window and not have to switch between tabs.
FLast edited by russofris; 03 March 2012, 12:04 PM.
Leave a comment:
-
Any upcoming benchmark with transparent FS compression on Phoronix ?
Leave a comment:
Leave a comment: