OCZ's Agility 2 Reviewed: The First SF-1200 with MP Firmware
by Anand Lal Shimpi on April 21, 2010 7:22 PM ESTWhile it happens a lot less now than a couple of years ago, I still see the question of why SSDs are worth it every now and then. Rather than give my usual answer, I put together a little graph to illustrate why SSDs are both necessary and incredibly important.
Along the x-axis we have different types of storage in a modern computer. They range from the smallest, fastest storage elements (cache) to main memory and ultimately at the other end of the spectrum we have mechanical storage (your hard drive). The blue portion of the graph indicates typical capacity of these storage structures (e.g. 1024KB L2, 1TB HDD, etc...). The further to the right you go, the larger the structure happens to be.

The red portion of the graph lists performance as a function of access latency. The further right you go, the slower the storage medium becomes.
This is a logarithmic scale so we can actually see what’s going on. While capacity transitions relatively smoothly as you move left to right, look at what happens to performance. The move from main memory to mechanical storage occurs comes with a steep performance falloff.
We could address this issue by increasing the amount of DRAM in a system. However, DRAM prices are still too high to justify sticking 32 - 64GB of memory in a desktop or notebook. And when we can finally afford that, the applications we'll want to run will just be that much bigger.
Another option would be to improve the performance of mechanical drives. But we’re bound by physics there. Spinning platters at more than 10,000 RPM proves to be power, sound and reliability prohibitive. The majority of hard drives still spin at 7200 RPM or less.
Instead, the obvious solution is to stick another level in the memory hierarchy. Just as AMD/Intel have almost fully embraced the idea of a Level 3 cache in their desktop/notebook processors, the storage industry has been working towards using NAND as an intermediary between DRAM and mechanical storage. Let’s look at the same graph if we stick a Solid State Drive (SSD) in there:

Not only have we smoothed out the capacity curve, but we’ve also addressed that sharp falloff in performance. Those of you who read our most recent VelociRaptor VR200M review will remember that we recommend a fast SSD for your OS/applications, and a large HDD for games, media and other large data storage. The role of the SSD in the memory hierarchy today is unfortunately user-managed. You have to manually decide what goes on your NAND vs. mechanical storage, but we’re going to see some solutions later this year that hope to make some of that decision for you.
Why does this matter? If left unchecked, sharp dropoffs in performance in the memory/storage hierarchy can result in poor performance scaling. If your CPU doubles in peak performance, but it has to wait for data the majority of the time, you’ll rarely realize that performance increase. In essence, the transistors that gave your CPU its performance boost will have been wasted die area and power.
Thankfully we tend to see new levels in the memory/storage hierarchy injected preemptively. We’re not yet at the point where all performance is bound by mass storage, but as applications like virtualization become even more prevalent the I/O bottleneck is only going to get worse.
Motivation for the Addiction
It’s this sharp falloff in performance between main memory and mass storage that makes SSDs so enticing. I’ve gone much deeper into how these things work already, so if you’re curious I’d suggest reading our SSD Relapse.
SSD performance is basically determined by three factors: 1) NAND, 2) firmware and 3) controller. The first point is obvious; SLC is faster (and more expensive) than MLC, but is limited to server use mostly. Firmware is very important to SSD performance. Much of how an SSD behaves is determined by the firmware. It handles all data mapping to flash, how to properly manage the data that’s written on the drive and ensures that the SSD is always operating as fast as possible. The controller is actually less important than you’d think. It’s really a combination of the firmware and controller that help determine whether or not an SSD is good.
For those of you who haven’t been paying attention, we basically have six major controller manufacturers competing today: Indilinx, Intel, Micron, Samsung, SandForce and Toshiba. Micron uses a Marvell controller, and Toshiba has partnered up with JMicron on some of its latest designs.
Of that list, the highest performing SSDs come from Indilinx, Intel, Micron and SandForce. Micron makes the only 6Gbps controller, while the rest are strictly 3Gbps. Intel is the only manufacturer on our shortlist that we’ve been covering for a while. The rest of the companies are relative newcomers to the high end SSD market. Micron just recently shipped its first competitive SSD, the RealSSD C300 as did SandForce.

We first met Indilinx a little over a year ago when OCZ introduced a brand new drive called the Vertex. While it didn’t wow us with its performance, OCZ’s Vertex seemed to have the beginnings of a decent alternative to Intel’s X25-M. Over time the Vertex and other Indilinx drives got better, eventually earning the title of Intel alternative. You wouldn’t get the same random IO performance, but you’d get better sequential performance and better pricing.
Several months later OCZ introduced another Indilinx based drive called Agility. Using the same Indilinx Barefoot controller as the Vertex, the only difference was Agility used 50nm Intel or 40nm Toshiba NAND. In some cases this resulted in lower performance than Vertex, while in others we actually saw it pull ahead.

OCZ released many other derivatives based on Indilinx’s controller. We saw the Vertex EX which used SLC NAND for enterprise customers, as well as the Agility EX. Eventually as more manufacturers started releasing Indilinx based drives, OCZ attempted to differentiate by releasing the Vertex Turbo. The Vertex Turbo used an OCZ exclusive version of the Indilinx firmware that ran the controller and external DRAM at a higher frequency.
Despite a close partnership with Indilinx, earlier this month OCZ announced that its next generation Vertex 2 and Agility 2 drives would not use Indilinx controllers. They’d instead be SandForce based.



61 Comments
View All Comments
geekfool - Wednesday, April 21, 2010 - link
He already reviewed Vertex LEhttp://www.anandtech.com/show/2899
http://www.anandtech.com/show/2944/9
Only 5000 were made. Reply
529th - Thursday, April 22, 2010 - link
Some people are curious about the Vertex LE 50g version. Yes, I've read the Vertex LE 100g review :)50g Vertex LE: http://www.newegg.com/Product/Product.aspx?Item=N8...
New Egg's description says "For enthusiasts w/ up to 15,000 4KB random write IOPS" which would suggest the controller is the SF 1200 where as the Vertex LE SSD drives are suppose to have the SF 1500 controller which will do ~ 30,000 4kb so the inconsistency brings up curiosity. To make matters worse, The OCZ website says they use the SF 1500 controller. Which I vaguely recall someone saying they asked OWC which controller they were using for their OWC Mercury Extreme SSD drives and OWC's response was that they didn't know.... Reply
willscary - Thursday, April 22, 2010 - link
Originally, I was told by Customer Service that he "did not know", but after pressing for an answer and a breif period on hold, he returned and told me that all current and future Mercury Extreme SSDs would utilize the Sandforce 1200 controller.I was very angry at this "bait and switch" and returned my SSDs. Actually, they were in transit and I had OWC recall them. I have not yet received credit for them although they returned to OWC early Tuesday morning.
I will also say that OWC did send confirmation of the returns and said that the credit would be processed by the end of the week, so all is not bad.
I was asked "what the big deal was" on another thread. The way I see it, it would be like ordering an expensive sports car with a V6 and having it arrive with a turbocharged 4 cylinder. The performance may be the same, but there would then be the possibility of added maintenance costs, lesser reliability and a shorter lifespan. Add to that that the dealer would tell me that even though the smaller turbo option was $1,000 less than the V6, I should pay the same because performance really would be nearly identical.
Just my thoughts. Reply
DanNeely - Thursday, April 22, 2010 - link
15k IOPs is higher than the SF1200 supports with a normal firmware. More likely I think would be something similar to intels 40GB drive where only half the controllers flash chip ports are filled and a full speed SF controller. Replyspeden - Wednesday, April 21, 2010 - link
I still don't understand if the SandForce compression increases the available storage space. Is that discussed in the article somewhere? Is the user storage capacity 93.1 GB if you write uncompressable data, but much larger if you are writing normal data? If so that would effectively lower the cost per gigabyte quite a bit. ReplyRyan Smith - Wednesday, April 21, 2010 - link
It does not increase the storage capacity of the drive. The OS still sees xxGB worth of data as being on the drive even if it's been compressed by the controller, which means something takes up the same amount of reported space regardless of compressibility.The intention of SandForce's compression abilities was not to get more data on to the drive, it was to improve performance by reading/writing less data, and to reduce wear & tear on the NAND as a result of the former.
If you want to squeeze more storage space out of your SSD, you would need to use transparent file system compression. This means the OS compresses things ahead of time and does smaller writes, but the cost is that the SF controller won't be able to compress much if anything, negating the benefits of having the controller do compression if this results in you putting more data on the drive. Reply
arehaas - Thursday, April 22, 2010 - link
The Sandforce drives report the same space available to the user, even if there is less data written to the drive. Does it mean that Sandforce drives should last longer because there are fewer actual writes to the NAND? One would reach the 10 million (or whatever) writes with Sandforce later than with other drives. ReplyRyan Smith - Thursday, April 22, 2010 - link
Exactly. ReplyMadMan007 - Wednesday, April 21, 2010 - link
On a note somewhat related to another post here, I have a request. Could you guys please post final 'available to OS' capacity in *gibibytes*? (or if you must post gigabytes to go along with the marketers at the drive companies make it clear you are using GIGA and not GIBI) After I realized how much 'real available to OS' capacity can vary among drives which supposedly have the same capacity this would be very useful information...people need to know how much actual data they can fit on the drives and 'gibibytes available to the OS' is the best standard way to do that. Replyvol7ron - Wednesday, April 21, 2010 - link
Attach all corrections to this post.1st Paragraph: incredible -> incredibly Reply