4 ms·
I agree, I think there is often a faulty assumption by many developers doing benchmarking that their underlying environment doesn't matter. Often I see performa
by Klinky 4y ago
I agree, I think there is often a faulty assumption by many developers doing benchmarking that their underlying environment doesn't matter. Often I see performance results posted with little mention of the details of the environment. At least here they posted they were using a high-end SSD, but note they just say they're on a "Dell XPS 13", as if there aren't multiple variants of that model produced every year for the last 5 or 6 years.
You're probably also right their multiple test runs resulted in the OS caching data, and a lot of the test runs may have just been testing in-memory performance instead of raw storage I/O performance.
- benhoyt 4y agoFair call about "Dell XPS 13". I've now clarified in the article (it's a recent 2022 Dell XPS 13 Plus). Regarding OS caching: I'm trying to avoid this by clearing caches with the "sysctl vm.drop_caches=3" command. Note that I show both cached and uncached numbers.
- Klinky 4y agoIt would still be good to call out the exact processor model, as the lowest end i5-1240P has half the L3 cache as the highest i7-1280P. Also I don't think it was clear you were running "sysctl vm.drop_caches=3" between benchmarking runs of your optimizations. Your table seemed to indicate those were generic initial read/write benchmarks from either dd or hardparm. The site you linked to also had comments on it stating dd is not very good for benchmarking, suggesting fio & a different site[1]. 1. https://linuxreviews.org/HOWTO_Test_Disk_I/O_Performance https://linuxreviews.org/HOWTO_Test_Disk_I/O_Performance