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 and unlike our Iometer tests, 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.

We quantify performance on this test by reporting the drive's average data throughput, a few data points about its latency, and the total energy used by the drive over the course of the test.

AnandTech Storage Bench - The Destroyer (Data Rate)

The Destroyer isn't enough to really challenge the 4TB 850 EVO, as this test doesn't write enough data to fill the drive even halfway. The 1TB 850 Pro still holds the record for the highest average data rate maintained by a SATA drive, but the 4TB EVO is closer to that than to any slower drive.

AnandTech Storage Bench - The Destroyer (Latency)

After the 2TB 850 Pro and EVO managed to tie with the top tier of drives for average service time, it is a little disappointing to see the 4TB 850 EVO only manages to match the 1TB models, but that's still high-end performance.

AnandTech Storage Bench - The Destroyer (Latency)AnandTech Storage Bench - The Destroyer (Latency)

The 4TB 850 EVO has slightly more extreme latency outliers than the 2TB 850s, but at the more strict threshold of 10ms it is tied with the 1TB 850 EVO for being the best TLC drive.

AnandTech Storage Bench - The Destroyer (Power)

The 4TB 850 EVO brings a little more reduction in power use over the 2TB 850 EVO, which substantially cut power use relative to the 1TB model. The 4TB drive is clearly not paying any significant penalty for keeping so much flash and DRAM powered up.

Performance Consistency AnandTech Storage Bench - Heavy
Comments Locked

145 Comments

View All Comments

  • profquatermass - Tuesday, August 9, 2016 - link

    6GB? My first hard drive was 200MB!
  • bug77 - Tuesday, July 12, 2016 - link

    Yeah, if you can get one of these at half the MSRP, it's only $750 :rolleyes:
  • Flunk - Monday, July 11, 2016 - link

    It's only $0.36 a GB, that's pretty cheap.
  • patrickjp93 - Monday, July 11, 2016 - link

    You can get something like the Sandisk Ultra II 1TB for 21 cents/GB.
  • ddriver - Monday, July 11, 2016 - link

    But then again why would you? Unless you are starving, and if you are, then you wouldn't be buying SSDs...

    I can't honestly think of any good reason to buy something other than samsung SSD - they have the most warranty and performance is top notch too, reliability seems to be better too.
  • FLHerne - Monday, July 11, 2016 - link

    Support and spec compliance. Samsung *still* ship firmware that claims support for queued TRIM ATA commands, but erases data if they're actually used. The consistent response is "Windows doesn't use these commands, we don't support other OS's", never mind that it's part of the SATA spec.

    (no, the kernel bug they fixed is completely unrelated)

    I *hate* manufacturers treating "works in current Windows" as an acceptable spec - it's guaranteed to shoot you in the foot down the line, as everyone saw with Vista. So I bought a SanDisk instead.
  • FLHerne - Monday, July 11, 2016 - link

    To clarify, I mean the way Vista broke all the manufacturers' stupid assumptions based on XP's behaviour.

    Also, the months it took for them to bodge around the performance degradation.
  • Notmyusualid - Tuesday, July 12, 2016 - link

    Acutally, I hate to back up Microsoft, but they DID say it was a complete re-write of Windows, and that it would not be the same OS at all.

    It performed horribly with low amounts of RAM, and at the time, the big RAM makers were in collusion over RAM price fixing (look it up), so that is why we saw laptops, with Vista being shipped with 256MB of RAM, which was a mess, I agree.

    But someone like myself, who had way more RAM than that, found it to be just fine. And it was way less infected than XP too.

    I guess your printer never received a Vista driver then? Too bad.

    But for me, and other client workstations with reasonable amounts of installed RAM I oversaw, it worked just fine, from the first day I used it.

    Flame away...
  • kepler- - Wednesday, July 13, 2016 - link

    Except they lied. Go onto your desktop and try to make a folder called "con". You can't, even on Windows 10, because they are still using code from Windows for Workgroups.

    There are a few others that (PRN, AUX, NUL, COM1...), which are all legacy Windows device names. They never '"rewrote" anything from the ground up.
  • Michael Bay - Thursday, July 14, 2016 - link

    Oy vey, muh geschafts can`t go into appropriate folders now!
    Such shoah.

Log in

Don't have an account? Sign up now