Final Words

To date, we have only seen asynchronous NAND in SandForce SSDs and now I can see why. SandForce gets away with asynchronous NAND because it does real-time compression, meaning that it writes less to the NAND and hence there is also less to read. That's why Agility 3 performs so well and in most cases its performance is equal to the Vertex 3. Compression is an efficient way of eliminating the NAND bottleneck as long as you're dealing with compressible data. Once you switch to incompressible data, there is a big difference between Vertex 3 and Agility 3, all due to the NAND interface.

Without a real time compression engine, the Agility 4 is considerably slower than its counterpart equipped with synchronous NAND. It's clear OCZ is using its clever performance mode to hide a lot of the limitations of using asynchronous NAND. As you fill the drive the Agility 4's peak write performance drops considerably. 

While Agility 4 is priced competitively, it's not cheap enough to be worth it. However, Vertex 4 is most likely a better investment in that case since it's only $5-20 more anyway.

Where the Agility 4 makes sense is when it's heavily discounted. As of late we've seen a couple of really hot deals on older SSDs. If you can find an Agility 4 for significantly less than the Crucial m4 or Samsung SSD 830 then it might be worth it. It's definitely faster than a mechanical drive at least. But at normal prices, the m4 or 830 for a little more would be a much better purchase.

Performance Over Time & TRIM
Comments Locked

41 Comments

View All Comments

  • Wardrop - Sunday, September 2, 2012 - link

    You guys should work on some kind type reporting method, e.g. when you highlight a portion of text in the article, is shows a button in the top-right (or bottom-right) of your selection with something like "report error". Clicking it yields a little popup form with a textarea and a submit button. On submit, it emails the author with the URL, the selected text containing the error, and the users comments.

    I'm not sure who your web developers is, but I personally wouldn't find this to be a difficult thing to implement in any of my Ruby applications (not Rails by the way), assuming you've already got some kind of popup framework. It'd be a matter of adding a bit of JavaScript into your article template/layout to handle the text selection button, and popup form. After that, it's just a matter of adding an endpoint on the server, e.g. http://www.anandtech.com/report_error/<article_... to handle the POST request and send the email off.

    It would be a two hour job probably, but it depends on the framework you guys are using obviously, and the experience of your developer in doing this kind of thing.

    Would be a worthy time investment considering that for every article, there's usually quite a number of typographic errors reported by users.
  • KZ0 - Sunday, September 2, 2012 - link

    If not for any other reason - at least not to bloat the comment section with typo reports. I love how responsive you guys at AT are to comments and critizism, and how fast you respond, but reading about corrected typos isn't that interesting.
  • maximumGPU - Tuesday, September 4, 2012 - link

    Agreed!
  • Impulses - Saturday, September 1, 2012 - link

    I find their performance mode more disturbing than even SF's performance gap with compressible vs incompressible data... Conclusion makes total sense, it'd have to be a rather large discount for me to consider it or recommend it over the m4, 830, or M5S... Add to that all the PR problems OCZ still has due to being the first name a lot of people think of regarding last year's SF fiasco, and OCZ has a long road ahead to grab some positive mind share again.
  • Zoomer - Saturday, September 1, 2012 - link

    For these results to be valid, the drive has to be at most half full. Thus, this 256 GB drive would be effectively only have 128GB of usable capacity...throwing $/GB out the window.
  • jb510 - Saturday, September 1, 2012 - link

    I asked Anand about this drive a month or so ago in comparison to the Crucial m4. In part due to his reply I ended up buying a m4 and have been very happy with it. Still glad to see the full report of the agility4, it was tempting at the time both the m4 & a4 were $400 with the a4 being substantially newer to market.
  • Runamok81 - Saturday, September 1, 2012 - link

    In a move reminiscent of OCZs villainous 32nm / 25nm debacle,
    http://www.anandtech.com/show/4256/the-ocz-vertex-...

    OCZ is shipping TWO flavors of this drive into the retail channel without informing consumers. It seems anandtech received the better performing (more reliable) micron NAND SSD. Why won't OCZ ship THEIR flavor of their drive for Anandtech to test?

    http://images.tweaktown.com/content/4/8/4881_10_oc...

    Along with its rumored increase in failure rates (tweaktown/newegg and amazon reviews), I'd be curious to see if there is a performance difference between the two flavors of the drives.

    Fool me once, shame on you OCZ! Fool us twice, who should be ashamed?
  • hybrid2d4x4 - Saturday, September 1, 2012 - link

    Asynchronous NAND drives had lower power consumption in past iterations - to what extent is this still true? How come there is no power consumption graph?

    Also, the A4 is slower overall in the storage bench tests than the Agility 3? What's going on here? This doesn't look like progress to me...
  • Kristian Vättö - Saturday, September 1, 2012 - link

    Vertex 4 and Agility 4 require special power testing hardware which I don't have (our regular tools don't work with them for some reason).

    As for Agility 3 vs Agility 4, as I said in the article, Agility 3 gets away with async NAND because of real-time compression used by SandForce.
  • chris81 - Saturday, September 1, 2012 - link

    Please make the same text which appears in all SSD reviews italic. It would ease skipping these:
    The four corners of SSD performance are as follows...

Log in

Don't have an account? Sign up now