AnandTech Storage Bench 2011 - Light Workload

Our new light workload actually has more write operations than read operations. The split is as follows: 372,630 reads and 459,709 writes. The relatively close read/write ratio does better mimic a typical light workload (although even lighter workloads would be far more read centric).

The I/O breakdown is similar to the heavy workload at small IOs, however you'll notice that there are far fewer large IO transfers:

AnandTech Storage Bench 2011 - Light Workload IO Breakdown
IO Size % of Total
4KB 27%
16KB 8%
32KB 6%
64KB 5%

Despite the reduction in large IOs, over 60% of all operations are perfectly sequential. Average queue depth is a lighter 2.2029 IOs.

AnandTech Storage Bench 2011 - Light Workload

Our light workload doesn't do very well on the F40 at all. As we discovered in our launch review, the heavy workload runs for long enough (~3 hours) that performance doesn't change from run to run. Our light workload however only takes around 30 - 45 minutes to run and thus we see a significant performance difference from one run to the next (after 2 runs the performance gains level off though). While the Intel SSD 311 climbs significantly in both runs, the F40 shows a marginal improvement in the first run and tops out at around 80MB/s regardless of what HDD it's paired with. Clearly we're hitting a bottleneck here, one that doesn't exist on the 311.

An obvious benefit of Intel's SSD 311 is that its firmware was designed with caching in mind, something that isn't true for standard SSDs used as a cache.

AnandTech Storage Bench 2011 - Light Workload

AnandTech Storage Bench 2011 - Light Workload

AnandTech Storage Bench 2011 - Light Workload

AnandTech Storage Bench 2011 - Light Workload

AnandTech Storage Bench 2011 - Light Workload

AnandTech Storage Bench 2011 - Heavy Workload Impact of SSD Size on Cache Performance
Comments Locked

81 Comments

View All Comments

  • jordanclock - Friday, May 13, 2011 - link

    I like the idea of this article and it starts providing some extra data that was asked for in the original review: What about other SSDs? Could we get some more SSDs tested with SRT? I'm not expecting Vertex 3s, but some "older" SSDs like the F40 that would likely be replaced soon.
  • MrSpadge - Friday, May 13, 2011 - link

    Currently Anand tested 3 mid- to high performance SSDs and I think this gives us a pretty good picture overall. However, if another one was tested I'd want the 64 GB Agility 3 and/or Solid 3. Well, a proper review of them would be very nice anyway ;)

    MrS
  • Cow86 - Friday, May 13, 2011 - link

    Yea I was thinking the same thing...they supposedly perform a lot better, while still being reasonably affordable for the 60GB drives (~110 euro's here). Maybe they'd be the ultimate cache at a reasonable price point? Either way would love a review of those as well, vertex 3 is staying rather expensive :(
  • jebo - Friday, May 13, 2011 - link

    I agree that the Agility 3 and Solid 3 look very promising.
  • therealnickdanger - Friday, May 13, 2011 - link

    Plus, SRT works with drives up to 64GB, so it seems worth it to test a drive of that size. I imagine there are many users (such as myself) that have older Intel 80GB, Indilix 64GB, or SandForce SF1200/1500 64GB drives that will soon be replaced with faster 6Gbps drives.

    I would imagine that you could a drive of any size, especially the larger ~120GB SSDs that offer significant speed advantages over the 64GB models. SRT would limit the usable cache to 64GB, but it would still be interesting to see...

    *wink**hint*
  • Boissez - Friday, May 13, 2011 - link

    Yup - Here's another vote for that article. I have an 'old' 60GB agility 2 boot drive and a Z68 board on it's way. Question now is whether I keep it as boot drive or whether I take a performance hit and use it as cache. This article comes close to answering it yet Anandtech's own SSD workload benchmarks (which are the most interesting IMO) does not include the F40's numbers.
  • GullLars - Tuesday, May 24, 2011 - link

    If you can fit your OS and core apps/games on your agility 2, it's a no-brainer, keep it as you have. If you have a lot of apps and games you have had on HDDs and use often, you could concider trying it as cache.
    I have 3 computers with 32GB boot drives (1 laptop, HTPC, and a donated SSD to my fathers computer), and all of them get by fine with that with a little bit of management. You could concider using 30GB for caching and 30GB for OS + core apps, getting full SSD speed on the stuff you use the most, and have cache help out on game loads and more seldom used apps.
  • Mr Perfect - Friday, May 13, 2011 - link

    That's what I'm thinking too. Get yourself the largest, fastest cache you can and see what happens. :) Currently that's looking like a 64GB Agility 3 or Solid 3.
  • samsp99 - Friday, May 13, 2011 - link

    I was just asking myself this very question...
  • genji256 - Friday, May 13, 2011 - link

    I'm confused. If the 311 performed better on the second run ("Intel 311 - Run 1" in your table), shouldn't that mean that the cache was large enough to store the data for all the applications (since they all ran during the first run)? If so, why would there suddenly be data evicted from the cache between the second and third run ("Intel 311 - Run 1" and "Intel 311 - Run 2" respectively)?

Log in

Don't have an account? Sign up now