AnandTech Storage Bench 2011

Two years ago we introduced our AnandTech Storage Bench, a suite of benchmarks that took traces of real OS/application usage and played them back in a repeatable manner. I assembled the traces myself out of frustration with the majority of what we have today in terms of SSD benchmarks.

Although the AnandTech Storage Bench tests did a good job of characterizing SSD performance, they weren't stressful enough. All of the tests performed less than 10GB of reads/writes and typically involved only 4GB of writes specifically. That's not even enough exceed the spare area on most SSDs. Most canned SSD benchmarks don't even come close to writing a single gigabyte of data, but that doesn't mean that simply writing 4GB is acceptable.

Originally I kept the benchmarks short enough that they wouldn't be a burden to run (~30 minutes) but long enough that they were representative of what a power user might do with their system.

Not too long ago I tweeted that I had created what I referred to as the Mother of All SSD Benchmarks (MOASB). Rather than only writing 4GB of data to the drive, this benchmark writes 106.32GB. It's the load you'd put on a drive after nearly two weeks of constant usage. And it takes a *long* time to run.

1) The MOASB, officially called AnandTech Storage Bench 2011 - Heavy Workload, mainly focuses on the times when your I/O activity is the highest. There is a lot of downloading and application installing that happens during the course of this test. My thinking was that it's during application installs, file copies, downloading and multitasking with all of this that you can really notice performance differences between drives.

2) I tried to cover as many bases as possible with the software I incorporated into this test. There's a lot of photo editing in Photoshop, HTML editing in Dreamweaver, web browsing, game playing/level loading (Starcraft II & WoW are both a part of the test) as well as general use stuff (application installing, virus scanning). I included a large amount of email downloading, document creation and editing as well. To top it all off I even use Visual Studio 2008 to build Chromium during the test.

The test has 2,168,893 read operations and 1,783,447 write operations. The IO breakdown is as follows:

AnandTech Storage Bench 2011 - Heavy Workload IO Breakdown
IO Size % of Total
4KB 28%
16KB 10%
32KB 10%
64KB 4%

Only 42% of all operations are sequential, the rest range from pseudo to fully random (with most falling in the pseudo-random category). Average queue depth is 4.625 IOs, with 59% of operations taking place in an IO queue of 1.

Many of you have asked for a better way to really characterize performance. Simply looking at IOPS doesn't really say much. As a result I'm going to be presenting Storage Bench 2011 data in a slightly different way. We'll have performance represented as Average MB/s, with higher numbers being better. At the same time I'll be reporting how long the SSD was busy while running this test. These disk busy graphs will show you exactly how much time was shaved off by using a faster drive vs. a slower one during the course of this test. Finally, I will also break out performance into reads, writes and combined. The reason I do this is to help balance out the fact that this test is unusually write intensive, which can often hide the benefits of a drive with good read performance.

There's also a new light workload for 2011. This is a far more reasonable, typical every day use case benchmark. Lots of web browsing, photo editing (but with a greater focus on photo consumption), video playback as well as some application installs and gaming. This test isn't nearly as write intensive as the MOASB but it's still multiple times more write intensive than what we were running in 2010.

As always I don't believe that these two benchmarks alone are enough to characterize the performance of a drive, but hopefully along with the rest of our tests they will help provide a better idea.

The testbed for Storage Bench 2011 has changed as well. We're now using a Sandy Bridge platform with full 6Gbps support for these tests.

AnandTech Storage Bench 2011 - Heavy Workload

We'll start out by looking at average data rate throughout our heavy workload test:

Heavy Workload 2011 - Average Data Rate

The overall score here is in-line with the SF-2281 solutions and OCZ's Octane. Our heavy workload is fairly write intensive, so I honestly expected the Vertex 4 to top the charts. Looking at the read/write breakdown explains why though:

Heavy Workload 2011 - Average Read Speed

Here we see the Vertex 4's poor low queue-depth sequential read performance rearing its head once more. Look at the sequential write speed and you'll see where OCZ makes up for its shortcomings however. The Vertex 4 writes quicker than any drive we've tested.

Heavy Workload 2011 - Average Write Speed

It's a tough tradeoff to come to terms with. The Vertex 4 delivers performance when it matters the most, but typically you want the absolute best performance regardless of workload. All of this may become moot if OCZ is able to address the situation with a firmware update in the coming weeks like it promised, but for buyers today it is something you have to think about.

The next three charts just represent the same data, but in a different manner. Instead of looking at average data rate, we're looking at how long the disk was busy for during this entire test. Note that disk busy time excludes any and all idles, this is just how long the SSD was busy doing something:

Heavy Workload 2011 - Disk Busy Time

Heavy Workload 2011 - Disk Busy Time (Reads)

Heavy Workload 2011 - Disk Busy Time (Writes)

Sequential Read/Write Speed AnandTech Storage Bench 2011 - Light Workload
Comments Locked

127 Comments

View All Comments

  • hechacker1 - Wednesday, April 4, 2012 - link

    I'm not really sure if they are buffering that much data. I'm betting a lot of it is to cache the state of the available flash (tables and bitmaps), and to provide lots of room so you can use memory intensive algorithms to allocate, sort, and combine data before it gets place on the flash.

    Even with some cache, just because the SSD is so fast, it's going to empty it in 1 second.
  • vegemeister - Monday, May 7, 2012 - link

    As long as it's not too much RAM to write out before the energy in the caps runs out, it's not really a problem.
  • 7Enigma - Wednesday, April 4, 2012 - link

    But you can show all these pretty specs and graphs but until you fix something like this catastrophe I will avoid your SSD's like the plague:

    Oh and what controller is in this beauty......Indilinx Everest!

    http://www.newegg.com/Product/Product.aspx?SID=PSa...
  • Comdrpopnfresh - Wednesday, April 4, 2012 - link

    It's nice to see the AES-256 encryption on it. That'll come in handy when the drive dies and has to be sent back to OCZ.
    I have 2 vertex2's and a vertex3, all of which died, and I have yet to eat or rma- OCZ provides no way to fulfill the warranty without compromising the security of user data. Used to be a big fan of OCZ, and loved their ssds... until this situation arose THREE TIMES.
  • vegemeister - Monday, May 7, 2012 - link

    Sure they do -- encrypt it yourself in software. Anyway, why would you trust OCZ not to be able to decrypt data encrypted by closed-source firmware designed by OCZ?
  • Hurk - Wednesday, April 4, 2012 - link

    where is the data for the 128gb version? it will be significantly different from the 256/512, and since im really loving SSD caching on new system builds, the smaller drive is more important to see the numbers for than the 256/512 for me.
  • Kristian Vättö - Wednesday, April 4, 2012 - link

    Manufacturers often send bigger capacities for reviews (they are the highest performing ones, after all). I'm sure there will be a 128GB review once we get one, which is hopefully sooner than later :-)
  • Reikon - Wednesday, April 4, 2012 - link

    Nice referral link there.
  • JarredWalton - Thursday, April 5, 2012 - link

    No worries -- they've been marked as spam and are gone now. Let this serve as a warning to others: if you try to put in a referral link in a comment and we mark you as spam, all your comments go bye bye!
  • iceman98343 - Thursday, April 5, 2012 - link

    sorry about that. c an you delete my last entry below. didn't see any TOS against referral links.

Log in

Don't have an account? Sign up now