The OCZ Vertex 3 Review (120GB)
by Anand Lal Shimpi on April 6, 2011 6:32 PM ESTThe Vertex 3 120GB
Whenever we review a new SSD many of you comment asking for performance of lower capacity drives. While we typically publish the specs for all of the drives in the lineup, we're usually only sampled a single capacity at launch. It's not usually the largest, but generally the second largest and definitely an indicator of the best performance you can expect to see from the family.
Just look at the reviews we've published this year alone:
Intel SSD 510 (240GB)
Intel SSD 320 (300GB)
Crucial m4 (256GB)
While we always request multiple capacities, it normally takes a little while for us to get those drives in.
When OCZ started manufacturing Vertex 3s for sale the first drives off of the line were 120GB, and thus the first shipping Vertex 3 we got our hands on was a more popular capacity. Sweet.
Let's first look at the expected performance differences between the 120GB Vertex 3 and the 240GB drive we previewed earlier this year:
| OCZ Vertex 3 Lineup | |||||
| Specs (6Gbps) | 120GB | 240GB | 480GB | ||
| Max Read | Up to 550MB/s | Up to 550MB/s | Up to 530MB/s | ||
| Max Write | Up to 500MB/s | Up to 520MB/s | Up to 450MB/s | ||
| 4KB Random Read | 20K IOPS | 40K IOPS | 50K IOPS | ||
| 4KB Random Write | 60K IOPS | 60K IOPS | 40K IOPS | ||
| MSRP | $249.99 | $499.99 | $1799.99 | ||
There's a slight drop in peak sequential performance and a big drop in random read speed. Remember our discussion of ratings from earlier? The Vertex 3 was of course rated before my recent conversations with OCZ, so we may not be getting the full picture here.
Inside the 120GB Vertex 3 are 16 Intel 25nm 64Gbit (8GB) NAND devices. Each device has a single 25nm 64Gbit die inside it, with the capacity of a single die reserved for RAISE in addition to the typical ~7% spare area.
The 240GB pre-production drive we previewed by comparison had twice as many 25nm die per package (2 x 64Gbit per NAND device vs. 1 x 64Gbit). If you read our SF-2000 launch article one of the major advantages of the SF-2000 controller has over its predecessor is the ability to activate twice as many NAND die at the same time. What does all of this mean for performance? We're about to find out.
RC or MP Firmware?
When the first SF-1500/1200 drives shipped last year they actually shipped with SandForce's release candidate (RC) firmware. Those who read initial coverage of the Corsair Force F100 drives learned that the hard way. Mass production (MP) firmware followed with bug fixes and threatened to change performance on some drives (the latter was resolved without anyone losing any performance thankfully).
Before we get to the Vertex 3 we have to talk a bit about how validation works with SandForce and its partners. Keep in mind that SandForce is still a pretty small company, so while it does a lot of testing and validation internally the company leans heavily on its partners to also shoulder the burden of validation. As a result drive/firmware validation is split among both SandForce and its partners. This approach allows SF drives to be validated heavier than if only one of the sides did all of the testing. While SandForce provides the original firmware, it's the partner's decision whether or not to ship drives based on how comfortable they feel with their validation. SandForce's validation suite includes both client and enterprise tests, which lengthens the validation time.
The shipping Vertex 3s are using RC firmware from SandForce, the MP label can't be assigned to anything that hasn't completely gone through SandForce's validation suite. However, SF assured me that there are no known issues that would preclude the Vertex 3 from being released today. From OCZ's perspective, the Vertex 3 is fully validated for client use (not enterprise). Some features (such as 0% over provisioning) aren't fully validated and thus are disabled in this release of the firmware. OCZ and SandForce both assure me that the SF-2200 has been through a much more strenuous validation process than anything before it.
Apparently the reason for OCZ missing the March launch timeframe for the Vertex 3 was a firmware bug that was discovered in validation that impacted 2011 MacBook Pro owners. Admittedly this has probably been the smoothest testing experience I've encountered with any newly launched SandForce drive, but there's still a lot of work to be done. Regardless of the performance results, if you want to be safe you'll want to wait before pulling the trigger on the Vertex 3. SandForce tells me that the only difference between RC and MP firmware this round is purely the amount of time spend in testing - there are no known issues for client drives. Even knowing that, these are still unproven drives - approach with caution.
The Test
| CPU |
Intel Core i7 965 running at 3.2GHz (Turbo & EIST Disabled) Intel Core i7 2600K running at 3.4GHz (Turbo & EIST Disabled) - for AT SB 2011, AS SSD & ATTO |
| Motherboard: |
Intel DX58SO (Intel X58) Intel H67 Motherboard |
| Chipset: |
Intel X58 + Marvell SATA 6Gbps PCIe Intel H67 |
| Chipset Drivers: |
Intel 9.1.1.1015 + Intel IMSM 8.9 Intel 9.1.1.1015 + Intel RST 10.2 |
| Memory: | Qimonda DDR3-1333 4 x 1GB (7-7-7-20) |
| Video Card: | eVGA GeForce GTX 285 |
| Video Drivers: | NVIDIA ForceWare 190.38 64-bit |
| Desktop Resolution: | 1920 x 1200 |
| OS: | Windows 7 x64 |
Facebook
Twitter
RSS
153 Comments
View All Comments
kensiko - Thursday, April 7, 2011 - link
It's true, I never saw any big company letting customers having so much impact on them. The forum is really the big thing here.lukechip - Wednesday, April 6, 2011 - link
I've just bought an 80GB Vertex 2. OCZ state that only "E" parts are affected, but at StorageReview, they show that they had a non "E" part which contained 25nm NAND. Also, OCZ say that the only parts affected are the 60 GB and 120 GB models.I've just purchased an 80 GB model, and have no idea what is inside it, nor whether I'd prefer it to be an 'old' one or a 'new' one.
The new SKUs that Anand listed indicate that moving forwards, all 80, 160 and 200 GB Vertex 2 units will be 25nm only, and all 60, 120 and 240 GB Vertex 2 units will be 34nm only. I can't imagine they can keep this up for long, as 34nm runs out and they have to move the 60, 120 and 240 GB models to 25 nm.
What I suspect is that prior to 25 nm NAND becoming available, all 80 GB units used the Hynix 32 nm NAND. Based on Anand's tests, I suspect this mean they were the worst performing units in the line up. 80 GB units built using the new 25 nm NAND would actually perform better than those built with Hynix 32 nm NAND.
So whereas 60 GB and 120 GB customers really want to have a unit based on 34 nm NAND, 80 GB customers like me really want to have a drive based on 25 nm NAND. Hence OCZ are not offering replacements for 80 GB units. A new 80 GB unit is better than an old 80 GB unit, even though it is not as good as an old 60 GB unit
So my questions are:
1/ Is what I am suggesting above true ?
2/ How can I tell what NAND I've got ? I've updated the firmware on my 80 GB unit soon after buying it, so the approach of using firmware version to determine NAND type doesn't seem too reliable to me ?
Personally, I find my unit plenty fast enough. And I understand that OCZ and other SSD vendors must accomodate what their suppliers present them with. However the lack of tranparency, and the "lucky dip" approach that we have to take when buying an SSD from OCZ lead me to conclude that they
1/ don't respect their customers and/or
2/ are very naive and stupid to expect that customers won't notice them pulling a 'bait and switch'
B3an - Thursday, April 7, 2011 - link
Anand... you seem to have forgotten something in your conclusion. You say it's best to go for the 240GB if torn between that and the 120GB. But being as two 120GB Vertex 3's are only very slightly more expensive than the 240GB version, wouldn't it make more sense to just get two 120GB's for RAID 0? Because you'd get considerably better performance than the 240GB then considering how well SSD's scale in RAID 0.Really great and interesting review BTW.
Alopex - Thursday, April 7, 2011 - link
I'd really like to see this question addressed, as well. According to several tests, SSDs scale in pretty much all categories after a minimal queue depth. It seems like the random reads here are the 120gb model's achilles' heel, but given the linearity of the scaling, it might be safe-ish to assume that 2x 120gb RAID 0 will equal 1x 240gb. For nearly the same price, it would then seem you get the same storage size, fixed the discrepancy between the two models, and hopefully see significant performance gains in the other categories like sequential read/write.I'm building a new computer at the moment, and in light of this article, I'm still planning to go with 2x 120gb Vertex 3s in RAID 0, unless someone can provide a convincing argument to do otherwise. At the moment, the only thing that really makes me hesitate is to see what the other vendors have planned for "next-gen" SSD performance. Then again, if I had that attitude I'd be waiting forever ;-)
Many thanks for the article, though!
casteve - Thursday, April 7, 2011 - link
No TRIM available in RAID.B3an - Thursday, April 7, 2011 - link
Not a big problem. I've had 3 different SSD sets in RAID 0 over the years, and i've not needed TRIM. And a certain crappy OS with a fruity theme dont even support TRIM without a hack job.ComputerNovice22 - Thursday, April 7, 2011 - link
You wrote "In the worst case comparison the F120 we have here is 30% faster than your 34nm Hynix Vertex 2."
I believe you meant 32nm Hynix, I'm not sure I'm right or not and I'm not trying to be one of those people that just likes to be right either, just wanted to let you know just in-case.
On another note though I LOVE the article, I bought a vertex 2 recently and I was very angry with OCZ after I hooked it up and realized it was a 25nm SSD ... I ended up just buying a 120Gb (510 elm-crest)
Lux88 - Thursday, April 7, 2011 - link
1. Thank you for investigating NAND performance so thoroughly.2. Thank you for benching drives with "common" capacities.
3. Thank you for protecting consumer interests.
Great article. Great site. Fantastic Anand.
sor - Thursday, April 7, 2011 - link
I worked at a Micron test facility years ago. I can only speak for DRAM, but I imagine NAND is much the same. Whenever someone drops a tray of chips and they go sprawling all over the floor... SpekTek. Whenever a machine explodes and starts crunching chips... SpekTek. I used to laugh when I saw PNY memory in BestBuy with a SpecTek mark on its chips selling for 2x what good RAM at newegg would cost.Basically anything that's dropped, damaged, or doesn't meet spec somehow, gets put into SpecTek and re-binned according to what it's now capable of. It's a brand that allows Micron to make money off of otherwise garbage parts, without diluting their own brand. On the good end the part may have just had some bent leads that needed to be fixed, on the bad end the memory can be sold and run at much slower specs or smaller capacity (blowing fuses in the chip to disable bad parts), or simply scrapped altogether.
sleepeeg3 - Thursday, April 7, 2011 - link
Thanks for the info, but IMO the bottom line is if it works reliably and it allows them to deliver something at a lower price, I am all for it. If it backfires on them and they get massive failure rates, consumers will respond by buying someone else's product. That's the beauty of capitalism.