Linux File System Shootout

IpSo_ writes "Finally an extensive, human readable Linux file system benchmark has been unleashed upon us. Originally posted on the Linux Kernel mailing list, using two of the most popular benchmarking tools available, it compares all the major file systems, including their different mount options. The results are surprising."

Comments

human readable ?

[gokulpod]

I am sorry..all I see are numbers floating around. Does someone have a "human readable" summary of this ?

Cheaters!

[borgdows]

NTFS has been removed of the benchmark results because it was the best performer in every test!

Re:Cheaters!

[turgid]

NTFS is only there for compatibility with legacy systems (i.e. Windows) and as such, performance is not really relevant, becuase you'll probably be migrating all your data over to something better and Linux-native like Reiser.

i am a human

[mydigitalself]

and i cannot make head or tail of that. it should read "uber linux haxx0r geek readable". could someone please explain - in lamens terms, which one i should be using to stream my avi's off to my xbox (www.xboxmediaplayer.de) using SMB shares? ;)

Re:i am a human

[1u3hr]

please explain - in lamens terms,

Is that "layman's" or "lamer's"?

Re:Didn't jfs do well

[NTmatter]

SCO has never claimed to own JFS. But then again, tomorrow's an entirely new business day, and there's a whole million lines of code that SCO hasn't yet lay claim to. ...is anyone else afraid that SCO will try to use Quantum Mechanical principles to gain ownership of the entire Linux kernel? Now, I am not a quantum physicist, but if they don't show which 50% they claim to own, won't the system be in an undetermined state? Wouldn't that mean that SCO could own both halves of the kernel at the same time?

Perhaps SCO has only lay claim to one line? This would account for the manner in which the number of lines claimed has grown from 80 to a million. This can be explained through the uncertainty principle, and compound error. The one line in question has not been determined, but has a probability of being located within certain files.

Could someone with a better grasp of mathematics please aid in identifying the SCO constant of ownership uncertainty?

Here's my $699 now.

[clusterix]

Wow, it looks like SCO has the best filesystems for Linux with JFS and XFS.

Journaling!

[Anonymous Coward]

Juicy stories like this should be saved for Friday nights. ;)

You mean you're reading Slashdot on Friday nights? Get with the program, man, you're missing out on new technology! Us respectable geeks spend our Friday nights ordering "Cinemax On Demand," it even lets you pause and rewind. Good times for all.

I'll put my JFS (jackable Friday shows) against your JFS (journaling file systems) any day, especially on Friday. I bet journaling file systems don't come with a Flowmaster Hit-The-Ceiling Guarantee...

--
Rate Naked People at Fuck Meter (not work-safe!)

Re:Didn't jfs do well

[SpaceLifeForm]

Actually, it is SCO that is in an uncertain state, and we only have to open the box, and SCO will be dead!

Readable?

[Daniel Quinlan]

Yeah, I know when I'm trying to summarize performance, I always include 1871 different numbers in a set of tables. The boss loves that. Readers love that.

Sorry, I looked at the benchmark results and quickly reached total eye glaze over. I think it could be presented a lot more clearly.

Re:Eh.

[drfreak]

Really, those pesky filesystems just get in the way. Just cat file >>/dev/hda and be done with it.