AnandTech Storage Bench - The Destroyer

The Destroyer has been an essential part of our SSD test suite for nearly two years now. It was crafted to provide a benchmark for very IO intensive workloads, which is where you most often notice the difference between drives. It's not necessarily the most relevant test to an average user, but for anyone with a heavier IO workload The Destroyer should do a good job at characterizing performance.

AnandTech Storage Bench - The Destroyer
Workload Description Applications Used
Photo Sync/Editing Import images, edit, export Adobe Photoshop CS6, Adobe Lightroom 4, Dropbox
Gaming Download/install games, play games Steam, Deus Ex, Skyrim, Starcraft 2, BioShock Infinite
Virtualization Run/manage VM, use general apps inside VM VirtualBox
General Productivity Browse the web, manage local email, copy files, encrypt/decrypt files, backup system, download content, virus/malware scan Chrome, IE10, Outlook, Windows 8, AxCrypt, uTorrent, AdAware
Video Playback Copy and watch movies Windows 8
Application Development Compile projects, check out code, download code samples Visual Studio 2012

The table above describes the workloads of The Destroyer in a bit more detail. Most of the workloads are run independently in the trace, but obviously there are various operations (such as backups) in the background. 

AnandTech Storage Bench - The Destroyer - Specs
Reads 38.83 million
Writes 10.98 million
Total IO Operations 49.8 million
Total GB Read 1583.02 GB
Total GB Written 875.62 GB
Average Queue Depth ~5.5
Focus Worst case multitasking, IO consistency

The name Destroyer comes from the sheer fact that the trace contains nearly 50 million IO operations. That's enough IO operations to effectively put the drive into steady-state and give an idea of the performance in worst case multitasking scenarios. About 67% of the IOs are sequential in nature with the rest ranging from pseudo-random to fully random. 

AnandTech Storage Bench - The Destroyer - IO Breakdown
IO Size <4KB 4KB 8KB 16KB 32KB 64KB 128KB
% of Total 6.0% 26.2% 3.1% 2.4% 1.7% 38.4% 18.0%

I've included a breakdown of the IOs in the table above, which accounts for 95.8% of total IOs in the trace. The leftover IO sizes are relatively rare in between sizes that don't have a significant (>1%) share on their own. Over a half of the transfers are large IOs with one fourth being 4KB in size.

AnandTech Storage Bench - The Destroyer - QD Breakdown
Queue Depth 1 2 3 4-5 6-10 11-20 21-32 >32
% of Total 50.0% 21.9% 4.1% 5.7% 8.8% 6.0% 2.1% 1.4

Despite the average queue depth of 5.5, a half of the IOs happen at queue depth of one and scenarios where the queue depths is higher than 10 are rather infrequent. 

The two key metrics I'm reporting haven't changed and I'll continue to report both data rate and latency because the two have slightly different focuses. Data rate measures the speed of the data transfer, so it emphasizes large IOs that simply account for a much larger share when looking at the total amount of data. Latency, on the other hand, ignores the IO size, so all IOs are given the same weight in the calculation. Both metrics are useful, although in terms of system responsiveness I think the latency is more critical. As a result, I'm also reporting two new stats that provide us a very good insight to high latency IOs by reporting the share of >10ms and >100ms IOs as a percentage of the total.

AnandTech Storage Bench - The Destroyer (Data Rate)

The SM951 takes the lead easily and provides ~34% increase in data rate over the XP941. The advantage over some of the slower SATA 6Gbps drives is nearly threefold, which speaks for the performance benefit that PCIe and especially PCIe 3.0 provide.

AnandTech Storage Bench - The Destroyer (Latency)

The latency benefit isn't as significant, which suggests that the SM951 provides substantial boost in large IO performance, but the performance at small IO sizes isn't dramatically better.

AnandTech Storage Bench - The Destroyer (Latency)

Despite the lowest average latency, the SM951 actually has the most >10ms IO with nearly 2% of the IOs having higher latency than 10ms. I did some thermal throttling testing (see the dedicated page for full results) and the SM951 seems to throttle fairly aggressively, so my hypothesis is that the high number is due to throttling, which limits the drive's throughput momentarily (and hence increases the latency) to cool down the drive. 

AnandTech Storage Bench - The Destroyer (Latency)

However, the SM951 has the least >100ms IOs, which means that despite the possible throttling the maximum service times stay between 10ms and 100ms.

Performance Consistency AnandTech Storage Bench - Heavy
Comments Locked

128 Comments

View All Comments

  • Kristian Vättö - Wednesday, February 25, 2015 - link

    I didn't test any OCZ drives for this review because the Vector 180 NDA is due in a couple of days, so stay tuned.
  • IlikeSSD - Thursday, February 26, 2015 - link

    Vertex 460A is good enough to show the difference (maybe even Arc))
  • Shadowmaster625 - Wednesday, February 25, 2015 - link

    You should clip on a simple heatsink and run the tests again.
  • squatsh - Wednesday, February 25, 2015 - link

    Based on the orientation of the drive in it's M2 slot. (Ie is the controller facing up or down) Can it be made clear if we could just put a small thermal pad and one of those tiny heatsinks (like you can get for VRMs) on the controller (assuming that is what is overheating) in order to stop the thermal throttling on desktops and laptops with enough space.
  • Luke212 - Wednesday, February 25, 2015 - link

    what happened to the Intel P3500? It's been a year and nothing.
  • Mikemk - Wednesday, February 25, 2015 - link

    Comment 100

    Sorry, couldn't resist
  • awall13 - Thursday, February 26, 2015 - link

    Thanks for the great review. I like the changes in how the data is presented. One idea: In the performance consistency section, the steady-state performance could be presented with a single two-color bar per drive, with the full bar representing the average performance, and the shorter bar representing the average - 1 standard deviation. I'd still keep the second chart showing the standard deviation by itself, perhaps. Just a thought.
  • gseguin - Thursday, February 26, 2015 - link

    Performance performance performance. Ok, I get it, its fast and hard to find.
    Since we saw many issues crop up with the predecessors, with eventual fixes by Samsung, how much confidence is there in the drive itself from Anandtech... You know the controllers, you know the memory, you've covered different company's testing methodologies, how much confidence do you have in this product, and why is that absent from the introduction and final thoughts?
  • Kristian Vättö - Thursday, February 26, 2015 - link

    All Samsung's issues have been related to SSD with planar TLC NAND (i.e. 840 & 840 EVO). There is absolutely no reason to believe that the SM951 shares the issues because it's based on MLC NAND and Samsung's MLC NAND based SSDs have been flawless (830 & 840 Pro).
  • kgh00007 - Saturday, February 28, 2015 - link

    Hey, nice article. I like the new SSD test suite. Is there any way to add a long term read consistency test, or any sort of read consistency test in light of the Samsung 840 EVO issues?

    I'm an 840 EVO user with drops in read speed to below 50Mb/s. In fact I have never gotten the advertised 500MB/s read speeds on any SSD I own. Is that because I am using them as the boot drive?

    Do you test with the SSD as a second drive in the system? So taking out the overhead of the OS running on the drive as well as the test suite?

    Cheers, keep up the good work, I've been learning from this site for a long time....

Log in

Don't have an account? Sign up now