- Feb 13, 2025
- 3
- 0
- 10
If there's a page already written about this, apologies and I'd like to read it. The "how we test" article doesn't mention it. I found a post from 2023 here, but nobody actually gave information on IOMeter as Tom's uses it.
What are the test methods used by Tom's for IOMeter to test the pSLC cache size? Like IOMeter configuration and how they get the complete results and graph it. I've been trying it out using the Google Overview methods (which vary depending on how you phrase the search and I hate using it but couldn't find anything else), but it's very simplistic. There are references to things like "block size" that simply don't exist in the IOMeter GUI, and they recommend "multiple gigabytes" but "transfer request size" only allows up to 1023MB,1023KB,1023B. There are also only a few datapoints in the results.csv file, so I don't see how it's possible to graph out all the speeds at each amount of data written. I'm also getting ridiculous results, like 400MBps to 550MBps sequential on a drive that benchmarks at 1.7GBps writes.
What are the test methods used by Tom's for IOMeter to test the pSLC cache size? Like IOMeter configuration and how they get the complete results and graph it. I've been trying it out using the Google Overview methods (which vary depending on how you phrase the search and I hate using it but couldn't find anything else), but it's very simplistic. There are references to things like "block size" that simply don't exist in the IOMeter GUI, and they recommend "multiple gigabytes" but "transfer request size" only allows up to 1023MB,1023KB,1023B. There are also only a few datapoints in the results.csv file, so I don't see how it's possible to graph out all the speeds at each amount of data written. I'm also getting ridiculous results, like 400MBps to 550MBps sequential on a drive that benchmarks at 1.7GBps writes.
Facebook
Twitter
Instagram