AnandTech Storage Bench 2011

Last year 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. Anand assembled the traces 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 we 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. Later, however, we created what we refer to as the Mother of All SSD Benchmarks (MOASB). Rather than only writing 4GB of data to the drive, this benchmark writes 106.32GB. This represents 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. Our 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) We tried to cover as many bases as possible with the software 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 and WoW are both a part of the test), as well as general use stuff (application installing, virus scanning). We included a large amount of email downloading, document creation, and editing as well. To top it all off we 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 ranges 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 we're 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 we'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, we will also break out performance into reads, writes, and combined. The reason we 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. It has 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 last year.

We 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 new heavy workload test:

Heavy Workload 2011—Average Data Rate

The 840 is quite average in our Heavy suite and performs similarly to most SandForce drives. The 840 Pro is a lot faster under heavy workloads, so it should be obvious by now why Samsung is offering two SSDs instead of one like they used to.

Heavy Workload 2011—Average Read Speed

Heavy Workload 2011—Average Write Speed

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)

Performance vs. Transfer Size AnandTech Storage Bench 2011 - Light Workload
Comments Locked

86 Comments

View All Comments

  • roedtogsvart - Monday, October 8, 2012 - link

    Might have to finally replace my Intel 320 with this. Very nice review Kristian
  • Old_Fogie_Late_Bloomer - Monday, October 8, 2012 - link

    Both the Intel 320 and the Samsung 840 Pro support encryption...does the non-Pro 840 offer it or not? I'm swinging back towards getting an 840 Pro for my laptop because of the lack of encryption in consumer 830 drives.

    On a side note, I was disappointed to discover recently that my current desktop motherboard doesn't support hard drive passwords, which is a shame given the fact that my system disk (an Intel 320) does...oh well.
  • ekon - Monday, October 8, 2012 - link

    The ATA password-based encryption these drives use is beset with issues, flaky motherboard support being just one.

    http://communities.intel.com/thread/20537

    On top of which, it's very poorly documented, and notice how reviews give it nothing more than a passing mention without testing the feature. A TrueCrypt/DiskCryptor alternative it is not :-/
  • Samus - Tuesday, October 9, 2012 - link

    I've had my 320 for two years, no problems with encryption, ever.

    And I second roedtogsvart that I may FINALLY replace my aging SSD with one of these. I've been thinking Intel 520 for awhile but still don't trust Sandforce, even with Intel at the helm.

    Samsung and Crucial are keeping the controllers simple, which is why they have the most reliable drives outside of Intel's original X25-M/320 SSD's.
  • Old_Fogie_Late_Bloomer - Tuesday, October 9, 2012 - link

    When you say "these drives", do you mean the Intel 320, the Samsung 840 Pro, or both? My T430 supports hard drive passwords for the expressly-stated purpose of allowing for encrypted SSDs, which is why I'm looking at the 840 Pro in particular.

    It seems like the only downsides would be having to enter the password to use the computer, and having to use a motherboard that supports HD passwords to access the drive (so I couldn't just plug it into my current desktop if something were to happen to my laptop and it were off for repair or whatever).
  • ruberbacchus - Saturday, October 20, 2012 - link

    On one hand, it seems to me that the potential gains performance-wise with hardware-based rather than software-based encryption are enormous; particularly so on older computers with slower processors. On the other hand, an encryption solution that is not properly documented as well as thoroughly verified and verifiable does simply not exist as a solution; confidence in the implementation is essential to the deployment of encryption. Unfortunately, it seems impossible to obtain clear references to how encryption works in this new class of SSD's. I read somewhere that it should conform to the OPAL standard, which mandates hardware-embedded keys. I am not sure this is such a great idea, for two reasons:
    - the keys will potentially be known to the manufacturer;
    - the keys will be open to physical attacks on the chip controller.
    With TrueCrypt e.g., the user himself generates the encryption keys, the master key used for encrypting the data as well as the header key used to wrap the master key. The latter is tied to the user's password. With hardware-based encryption, passwords may be used for authentication, but the keys will not necessarily be derived from the password. Unchangeable encryption keys weakens the security. In order for the system to be trustworthy, the user should be able to generate and re-generate at will their own encryption keys. At the moment it is not clear this is the case.
  • GreenReaper - Wednesday, August 8, 2018 - link

    It's true. Although not necessarily the fault of the drives, either. My leased server was taken offline by the installation of SSDs which the hardware (or rather, its firmware) couldn't handle. I dumped the firmware logs and traced it to commands relating to ATA security. Don't know if it had been set by the previous users of the SSDs or whatever, but it managed to freeze up the entire controller.
  • A5 - Monday, October 8, 2012 - link

    I guess I'm old fashioned and don't throw away my laptop every 6 months, but a 3.5 year lifetime seems really really short.
  • crimson117 - Monday, October 8, 2012 - link

    Agreed; maybe for a video card, but I expect longer than 3.5 years out of my hard drives.
  • repoman27 - Monday, October 8, 2012 - link

    Really? I rarely expect a consumer grade HDD to last much longer than that these days. In fact, I've seen an alarming trend of drives failing just past the 2 year mark, and still within the 3 year warranty period. (RMA'd one last week even.)

Log in

Don't have an account? Sign up now