For testing, the drives are all wiped and reset to factory settings by HDDerase V4. We try to use free or easily available programs and some real world testing so you can compare our findings against your own system. This is a good way to measure potential upgrade benefits.
We are in the process of updating our testing procedures for NVMe SSD’s adding new tests, refining others and using the latest versions of CrystalDiskMark, ATTO and AS SSD benchmarks. For a time we will show both old and new screenshots of these benchmarks as we transition from the older tests to the newer ones. We will try and re-test as many of the previously reviewed NVMe drives as we can so as to build up new versions of our comparative performance graphs.
The test setup for the new tests are listed below. Each is run five times.
128KB Sequential Read / Write.
Transfer Request Size: 128KB Span: 8GB Thread(s): 1 Outstanding I/O: 1-32 Test Run: 20 minutes per test
4K Sustained Random Read / Write.
Transfer Request Size: 4KB Span: 80GB Thread(s): 4 Outstanding I/O: 1-32 Test Run: 20 minutes per test
4K Random 70/30 mix Read/Write.
Transfer Request Size: 4KB Span: 80GB Reads: 70% Writes: 30% Thread(s): 4 Outstanding I/O: 2 – 32 Test Run: 20 minutes
Main system:
Intel Core i7-7700K with 16GB of DDR4-3200 RAM, Sapphire R9 390 Nitro and an Asus Prime Z270-A motherboard.
Other drives:
Corsair Force MP500 480GB
Corsair Neutron NX500 800GB
Intel Optane Memory 32GB
Intel SSD760p 512GB
Kingston HyperX Predator 480GB
Kingston A1000 480GB
Kingston KC1000 960GB
OCZ RevoDrive 350 480GB
OCZ RevoDrive 3 x2 480GB
Patriot Hellfire 240GB
Plextor M9Pe(Y) 512GB
Plextor M8PeG 512GB
Plextor M6e Black Edition PCIe 256GB
PNY CS2030 240GB
Samsung SSD960 PRO 2TB
Samsung SSD960 EVO 1TB
Samsung SSD950 PRO 256GB
Samsung SM951 256GB
Samsung XP941 512GB
Toshiba OCZ RD400 512GB
Western Digital Black PCIe 512GB
Software:
Atto Disk Benchmark.
CrystalMark 3.0.3.
AS SSD.
IOMeter.
Futuremark PC Mark 8
All our results were achieved by running each test five times with every configuration. This ensures that any anomalies are removed from the results. TRIM is confirmed as running by typing ‘fsutil behavior query disabledeletenotify' into the command line. A response of ‘disabledeletenotify =0' confirms TRIM is active.