You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have not been able to find any information on this. The problem I have with it is that it seems inconsistent with the rest of the output, yet the results of the famous CrystalDiskMark are based on it.
It's as if the value in the column MB/s is actually MiB/s and the returned score is in MB/s... (And if that truly is the case, then it seems that the heading for the column should be corrected?)
The text was updated successfully, but these errors were encountered:
It appears as if you're using an outdated version of the tool. This change was made in the commit cc45491. The latest update to Diskspd can be downloaded from https://aka.ms/diskspd.
I would also expect that any tools that use Diskspd would specify the -Rxml option and consume the results in XML format. The XmlResultParser would then display the value in bytes. The conventions used are documented under Size conventions for DiskSpd parameters.
My apologies - the above is based on CrystalDiskMark 6.0.1 (which also uses the fact that you used to output the score as exit code). I didn't realize that this has already been addressed...
I have not been able to find any information on this. The problem I have with it is that it seems inconsistent with the rest of the output, yet the results of the famous CrystalDiskMark are based on it.
Example:
It's as if the value in the column MB/s is actually MiB/s and the returned score is in MB/s... (And if that truly is the case, then it seems that the heading for the column should be corrected?)
The text was updated successfully, but these errors were encountered: