AnandTech Storage Bench - The Destroyer

The Destroyer is an extremely long test replicating the access patterns of very IO-intensive desktop usage. A detailed breakdown can be found in this article. Like real-world usage, the drives do get the occasional break that allows for some background garbage collection and flushing caches, but those idle times are limited to 25ms so that it doesn't take all week to run the test. These AnandTech Storage Bench (ATSB) tests do not involve running the actual applications that generated the workloads, so the scores are relatively insensitive to changes in CPU performance and RAM from our new testbed, but the jump to a newer version of Windows and the newer storage drivers can have an impact.

We quantify performance on this test by reporting the drive's average data throughput, the average latency of the I/O operations, and the total energy used by the drive over the course of the test.

ATSB - The Destroyer (Data Rate)

The average data rate of the 1TB Samsung PM981 on The Destroyer is comparable to the 960 EVO 1TB and well ahead of any competing TLC-based drives like the Toshiba XG5. The 512GB PM981 is slower by a typical amount, and still faster than any of the non-Samsung drives of that size.

ATSB - The Destroyer (Average Latency)ATSB - The Destroyer (99th Percentile Latency)

The 1TB PM981 shows a substantial improvement over the average and 99th percentile latency scores of the 960 EVO, putting it close to the 960 PRO. The 512GB PM981 isn't as impressive, with latency scores that fall behind most MLC-based NVMe SSDs.

ATSB - The Destroyer (Average Read Latency)ATSB - The Destroyer (Average Write Latency)

The 1TB PM981 sets a new record (among flash-based SSDs) for average read latency on The Destroyer, shaving a few microseconds off the 960 PRO's performance. The average write latency can't quite keep up with the MLC-based 960 PRO that doesn't use SLC write caching. The smaller 512GB PM981 is competitive with most similarly-sized MLC-based drives, but slower than Samsung's 960 PRO.

ATSB - The Destroyer (99th Percentile Read Latency)ATSB - The Destroyer (99th Percentile Write Latency)

Samsung's 99th percentile read latency is nothing special, though the PM981 does offer clear improvement over the 960 EVO. The 99th percentile write latency of the 1TB PM981 is excellent and far better than the 1TB 960 EVO. The 512GB PM981 is clearly the fastest TLC-based drive of that size that we've tested, but it doesn't quite match the 99th percentile latency scores of the MLC-based competition.

Introduction AnandTech Storage Bench - Heavy
POST A COMMENT

53 Comments

View All Comments

  • skavi - Monday, December 4, 2017 - link

    Lol, tech isn't wine. If people aren't working to improve it, it won't get better. Reply
  • skavi - Monday, December 4, 2017 - link

    Lol, tech isn't wine. If people aren't working to improve it, it won't get better. Reply
  • WorldWithoutMadness - Friday, December 1, 2017 - link

    that and ram oligopoly. Almost reminded me of intel before ryzen. Reply
  • Drumsticks - Thursday, November 30, 2017 - link

    I doubt we'll see 1TB 3D XPoint in an m.2 form factor until at least the second generation of XPoint. Power consumption looks too high; you'd probably have to severely limit performance to get into m.2, or you'd need a massive unrealistic heatsink. Reply
  • UltraWide - Thursday, November 30, 2017 - link

    Yes, the people want to see 900p destroy these benchmarks!! :) Reply
  • romrunning - Thursday, November 30, 2017 - link

    I would love to see the Optane 900p results included as well. Reply
  • peevee - Thursday, November 30, 2017 - link

    Me too. Reply
  • mczak - Thursday, November 30, 2017 - link

    I miss the power draw numbers. Reply
  • Drazick - Thursday, November 30, 2017 - link

    I don't like those m.2 drives. Can't we have high bandwidth connection for 2.5 inch drives? It will have less thermal issues for desktop configurations. Reply
  • DanNeely - Thursday, November 30, 2017 - link

    That's the barely gained any traction outside of enterprise U.2 connection. Reply

Log in

Don't have an account? Sign up now