Is there a way to compare the effects of each filesystem in SSD wear? That would be interesting. Specifically, I'd like to know how much of a negative effect does journaling have. It may be really bad or it may be nearly anecdotal.
Announcement
Collapse
No announcement yet.
Linux 5.14 SSD Benchmarks With Btrfs vs. EXT4 vs. F2FS vs. XFS
Collapse
X
-
Michael thank you but these tests are of near-zero use for most people out there.
What about testing something more mundane and user-oriented?- The time to launch a distro of your choice (could be quite time consuming actually)
- The time to launch Gimp (yeah, takes a lot of time as well). For fun I'd test launching Photoshop CS2 in Wine as well as it involves reading a ton of files
- The time to unpack e.g. Linux 5.13 source, followed by sync (just to make sure buffers are flushed)
- The time to tar/archive a large enough number of small and medium size files + sync
- The the time to copy a decent size tree of files + sync
- The time to install a big enough rpm/deb file or a number of such files - sync is not normally necessary but I'd invoke it just in case
Time and time again you continue to benchmark for high-load enterprise servers, not end users.
I've got a lot more ideas for things which you could test but considering I've voiced them many times already I've got no hope. It's sad but what can I do. Those tests could be highly relevant for users.Last edited by avem; 27 August 2021, 03:27 PM.
- Likes 9
Comment
-
To really tease apart the differences between whatever he's testing, you often have to focus on the extremes.
And I don't even consider DB or VM testing with CoW to be out-of-bounds, although it would probably make sense also to test with nodatacow, or at least chrattr +C.
Originally posted by avem View PostI've got a lot more ideas for things which you could test but considering I've voiced them many times already I've got no hope. It's sad but what can I do.
- Likes 3
Comment
-
How do you automate that?
Comment
-
-
Originally posted by jacob View Post
Databases have their own data integrity mechanisms, they don't rely on the filesystem for that. Databases and VMs are the two use cases where disabling CoW makes sense.
If I'm having a database or a VM in production, I'll be having it on RAID1. If I have the performance headroom to use a fancy filesystem, then I'll be using the filesystem-specific facilities for RAID1. And if I'm doing all that, then it will be quite silly of me to deprive myself of self-healing properties of this storage stack.
- Likes 1
Comment
-
Originally posted by flower View Post
many hdds and ssds use crc32 internally to verify data. as btrfs uses crc32 too its pretty useless.
and there is still integritysetup - if you use an external drive for integrity it doesnt have ANY performance penality. i am using this in an raid10 setup for quite a while (checksum is sha256)
Filesystems like ZFS and BTRFS where created to detect and autocorrect (if set up to use multiple copies) silent bitrot that the simpler ECC:s cannot catch, there have been studies done on ZFS: https://research.cs.wisc.edu/adsl/Pu...ion-fast10.pdf
Disk corruptions are prevalent across a broad range of modern drives.In a recent study of 1.53 million disk drives over 41 months [7], Bairavasundaram et al. show that more than 400,000 blocks had checksum mismatches, 8% of which were discovered during RAID reconstruction, creating the possibility of real data loss.Last edited by F.Ultra; 27 August 2021, 07:33 PM.
- Likes 4
Comment
-
Originally posted by Etherman View PostHow do you automate that?
1. Run them once, make a screenshot, store it, run them twice, run a screen recording application in background - when it "sees" the required picture, your measure the time.
2. Run them once, see how much data has been read from the disk, run them twice, check how much time it's taken to read this amount of data from the disk. It would also require either running `echo 3 > /proc/sys/vm/drop_caches` prior or using nocache.
The second option is quite easy to automate.Last edited by avem; 27 August 2021, 07:59 PM.
Comment
Comment