File-System Benchmarks On The Intel X25-E SSD
Phoronix: File-System Benchmarks On The Intel X25-E SSD
Late last month we looked at the Intel X25-E Extreme SSD on Linux. We ran this high-performance solid-state drive within a System76 Serval Notebook and compared its performance to a Seagate Momentus 7200.2 SATA HDD. During that testing we were just using the default EXT3 file-system, but now we have taken the Intel X25-E SSD for another spin as we looked at its performance when using the ReiserFS, JFS, XFS, EXT3, and EXT4 file-systems.
I'd love to see reiser4 with cryptcompress on when your pulling in btrfs testing.
A basic mkfs.reiser4 -o create=ccreg40,compress=lzo1 for example.
It'll up the cpu usage, but it'd be interesting to see how much faster reiser4 is when seek times arn't involved.
Is it possible that files for compilation tests are all in cache already, so Kernel never touch file system code anyway, hence same results across the board? I don't see in TFA any measures taken for clearing cache between tests.
I wonder what could be the performance of the file systems specialized for solid state drives (JFFS2, YAFFS2, LogFS, UBIFS...). Any reason for not including them in this benchmark ?
Because they need direct access to the flash memory (via MTD), while SSD expose themselves as normal HDs (i.e. block devices).
Originally Posted by _pma
Far away from Linux kernel...
Originally Posted by Gentooer
... deeply burried somewhere in california.
Originally Posted by kraftman
encoding for filesystem benchmarking?
Why are those encoding tests used again and again to benchmark file-system performance? I mean all of the do basically linear reading/writing, and not only in this test the results never differ more than 10% -> useless.
What I would care more about is moving/creating/deleting files, system bootup time, kernel unpack&compile, find over a whole system ... something which really stresses a FS and the IO subsystem.
I also don't run aalib stuff in my terminal to benchmark my graphic hardware
Last edited by Linuxhippy; 03-16-2009 at 01:31 PM.