Conclusion, Pricing, and Final Thoughts
Did you get linked to this conclusion page on accident? Click here to go to the start of our review!
Conclusion:
Conclusion:


PROS:
- *Really* fast throughput – saturating SATA 6Gb/sec on the first iteration of the tech.
- Excellent IOPS scaling at higher queue depths.
CONS:
- Odd stutter observed on our batch file write test (possibly due to beta firmware).
- Performance at lower queue depths could be improved upon.
- Price (see below)
- 100G @ $525 ($5.25 / GB)
- 200G @ $775 ($3.87 / GB)
- 400G @ $1350 ($3.37 / GB)

Final retail view of the OCZ Vertex 3 Pro SSD
There is one line in the documentation that gives me hope: “Note: Vertex 3 client solution will be priced significantly lower. TBA.” There isn’t anything more than that mentioned but if we consider that OCZ might take away the “enterprise class over-provisioning” then its possible we could get the same $775 price tag associated with a 250GB or 240GB drive, lower the price to $3.10 / GB. That is noticeably better but still higher than I think consumers are going to want to pay so hopefully OCZ has some more surprises ready for us. Much will also depend on how the competing SATA 6G offerings are priced from Intel and others and since competition almost always benefits the consumer, bring it on!
As for the availability of the Vertex 3 Pro SSDs, we are told the company is aiming for a mid-March release though no one wanted to be pinned down to an exact date. If you are on the hunt for the fastest SATA storage device available, keep your eyes peeled!
Final Thoughts:
OCZ is the first to get next generation SandForce out the door. While this was an engineering sample with a few kinks to work out, it is clearly a very capable performer and is bound to make early adopters and power users drool with anticipation. Bulk file throughput exceeding half a Gigabyte per second is astonishing. What was previously only possible with an SSD RAID or PCIe SSD is now possible with a single 2.5″ SATA unit.
I’m holding back on an award for this one, only because of the engineering-level firmware we tested under. I’ll update this space once we can verify those issues have been corrected in shipping units.