-
Notifications
You must be signed in to change notification settings - Fork 14
Update to reflect recent "upstream" CDM test changes #3
Comments
Additional info:
And there is a 0x00 (0 Fill) test option too. According to a comment here: |
Take a look at my fork: https://github.com/0xFelix/fio-cdm It tries to mimic CrystalDiskMark 6. The results should be quite comparable. |
This is my python version with a lot of customizabilities (it works on Windows, too): https://github.com/OliverLew/fio-cdm |
Thanks for fixing my other issue. I don't know if you are generally interested in improving fio-cdm further, but I'm going to submit a couple of suggestions if that's OK.
At the moment, fio-cdm outputs the results of the following tests:
This used to be the same as older versions of Crystal Disk Mark, see for example:
But newer versions of Crystal Disk Mark seem to use the following tests by default:
I don't know why they changed, but it might be worth researching this to see if you can do the same in fio-cdm. https://crystalmark.info/software/CrystalDiskMark/manual-en/History.html may be a good place to start looking.
I also notice in that History file that in 5.0.0 they did "Changed test order (all read test -> all write test)". Again, I don't know if that's important, but it might be worth changing fio-cdm to do the same.
I don't expect we'll ever get to the point where fio-cdm results are directly comparable to CDM, but it would be good to get close.
The text was updated successfully, but these errors were encountered: