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.

I'm also reporting the total power consumed during the trace, which gives us good insight into the drive's power consumption under different workloads. It's better than average power consumption in the sense that it also takes performance into account because a faster completion time will result in less watt-hours consumed. Since the idle times of the trace have been truncated for faster playback, the number doesn't fully address the impact of idle power consumption, but nevertheless the metric is valuable when it comes active power consumption. 

AnandTech Storage Bench - The Destroyer (Data Rate)

The pausing issue of the 1TB 850 EVO mSATA also translates straight to our The Destroyer trace. While higher capacities are usually faster than smaller capacities in this test, the 1TB mSATA is about 15% slower than the 500GB M.2. Generally speaking the 850 EVO does very well at 500GB and above, but since Samsung's TLC V-NAND is 128Gbit in capacity and single-plane, the 250GB can't keep up with drives that are using smaller capacity NAND for higher parallelism.

AnandTech Storage Bench - The Destroyer (Latency)

The latency graph further illustrates the poor performance of the 1TB mSATA, but quite surprisingly the 500GB 850 EVO is actually faster than the 512GB 850 Pro. I suspect the additional over-provisioning helps because The Destroyer is a very intensive trace that practically puts the drive into steady-state .

AnandTech Storage Bench - The Destroyer (Latency)

The share of high latency IOs is a bit high, but nothing to be concerned of. Only the 250GB model has a significant amount of >10ms IOs and for IO intensive workloads I would strongly advise to go with 500GB or higher. 

AnandTech Storage Bench - The Destroyer (Latency)

Active power consumption seems to be quite high for the 850 EVO, although I'm not surprised since TLC generally consumes more power than MLC due to its inherent design (more program pulses needed to achieve the final voltage state). 

AnandTech Storage Bench - The Destroyer (Power)

Performance Consistency AnandTech Storage Bench - Heavy
POST A COMMENT

58 Comments

View All Comments

  • Peichen - Tuesday, March 31, 2015 - link

    Shouldn't mSATA/M.2 intereface drives be a lot faster than SATAIII drives due to the much faster interface? I was kinda expecting 1GB/sec. speed consider there are already drive tested at 1.4 and 2.7GB/sec. Reply
  • MrCommunistGen - Tuesday, March 31, 2015 - link

    mSATA is SATA in a different formfactor. M.2 can be either SATA or PCI-E. As stated in the article, this drive comes (only) in the SATA form. Reply
  • foxtrot1_1 - Tuesday, March 31, 2015 - link

    The interface is still SATA, even if the connector is M.2. I assume PCIe M.2 drives will be coming later. Reply
  • Murloc - Tuesday, March 31, 2015 - link

    in a very short time they introduced a bunch of connectors and interfaces and it's all gotten quite confusing. Reply
  • foxtrot1_1 - Tuesday, March 31, 2015 - link

    Don't worry, it's not like there's also three different mainstream USB standards with two different plugs. Oh wait.

    Well, at least we have one agreed-upon display connection, that makes shopping for monitors and graphics cards easier. Oh wait.
    Reply
  • lazarpandar - Tuesday, March 31, 2015 - link

    That's the great thing about standards, you've got so many to choose from! Reply
  • yslee - Tuesday, March 31, 2015 - link

    xkcd #927 puts it very nicely. :P Reply
  • Artuk - Wednesday, April 1, 2015 - link

    Nice Reply
  • blanarahul - Tuesday, March 31, 2015 - link

    You need yo put /sarcasm tag so people don't get confused. Reply
  • Callitrax - Tuesday, March 31, 2015 - link

    One thing you should probably do in M.2 SSD reviews is include how the drives are keyed, preferably in one of the tables. This is important since the M.2 interface is actually 4 semi compatible "standards" (see http://arstechnica.com/gadgets/2015/02/understandi... As a result not all M.2 SSDs will fit in all M.2 slots. This one appears to be both B and M keyed so I think it should be pretty universal, but as an example the Samsung XP941 is only M keyed and thus will not work in the HP Stream Mini's B keyed SSD slot. (Did whoever came up with M.2 make a crappy standard that will cause lots of customer support calls and RMA's when consumers M.2 drives don't work with their M.2 equipped computers? Yes they did.) Reply

Log in

Don't have an account? Sign up now