On Tue, Jul 31, 2012 at 10:30:42PM -0700, Marc MERLIN wrote: > First: btrfs is the slowest: > gandalfthegreat:/mnt/ssd/var/local# time du -sh src/ > 514M src/ > real 0m25.741s > > Second: ext4 with mkfs.ext4 -O extent -b 4096 /dev/sda3 > gandalfthegreat:/mnt/mnt3# reset_cache > gandalfthegreat:/mnt/mnt3# time du -sh src/ > 519M src/ > real 0m12.459s > gandalfthegreat:~# grep mnt3 /proc/mounts > /dev/sda3 /mnt/mnt3 ext4 rw,noatime,discard,data=ordered 0 0 > > A freshly made ntfs filesystem through fuse is actually FASTER! > gandalfthegreat:/mnt/mnt2# reset_cache > gandalfthegreat:/mnt/mnt2# time du -sh src/ > 506M src/ > real 0m8.928s > gandalfthegreat:/mnt/mnt2# grep mnt2 /proc/mounts > /dev/sda2 /mnt/mnt2 fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0 > > How can ntfs via fuse be the fastest? To provide closure to this thread. I owed everyone an update, which I just finished typing: http://marc.merlins.org/perso/linux/post_2012-08-15_The-tale-of-SSDs_-Crucial-C300-early-Death_-Samsung-830-extreme-random-IO-slowness_-and-settling-with-OCZ-Vertex-4.html Basically, the samsung 830 just sucks. I got 2 of them, they both utterly sucked. There is no excuse for an SSD being several times slower than a slow hard drive on _READs_ (not even talking about writes). I'm not sure how I could have gotten 2 bad drives from Samsung in 2 different shipments, so I'm afraid the entire line may be bad. At least, it was for me after extensive benchmarking, and even using their own windows benchmarking tool. In the end, I got a OCZ Vertex 4 and it's superfast as per the benchmarks I posted in the link above. As good news, ext4 is faster than btrfs in my (limited) tests across both SSDs and my hard drive. Cheers, Marc -- "A mouse is a device used to point at the xterm you want to type in" - A.S.R. Microsoft is to operating systems .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html