Final Words

After years of begging, OCZ has finally delivered much of what we've wanted in an SSD: low write amplification and very good random/sequential write performance. It could use a more aggressive real-time garbage collection algorithm but running an OS with TRIM, that's mostly picking nits. The Vertex 4 takes write performance seriously and delivers handsomely, besting even the latest from Intel and Samsung. The advantage over SandForce is clear, particularly because Everest 2 and the Vertex 4 are able to deliver consistent performance regardless of data composition. SandForce's realtime compression/dedupe technology is definitely exciting, but if you're able to deliver similar or better performance without the inconsistency of data-dependency the choice is obvious. SandForce definitely set the bar very high with the SF-2281, but Everest 2 has the potential to exceed it - assuming OCZ/Indilinx can deliver on its promises.

Sequential read performance is unfortunately just as important for client workloads, and the Vertex 4 doesn't do nearly as well there. If OCZ is able to improve its low queue depth sequential read performance through a firmware update in the coming weeks, it will truly have built a drive (and controller) that are among the fastest on the market. I see no reason that OCZ shouldn't be able to achieve this given the sequential read performance we saw from Octane, but as is always the case with these types of launches we have to review the product we have, not the product we'll get.

Should nothing change, the tradeoff is an interesting one. OCZ effectively gives us three of the four corners of raw performance, and competitive sequential read speeds under heavy load. Does giving up the bottom end of sequential read performance matter? For users with very write intensive or generally IO heavy workloads, the tradeoff is likely worth it. It almost feels like OCZ should have launched the enterprise version of the Vertex 4 first, given its strengths. For more typical mainstream client workloads, the Vertex 4 isn't as good of a fit. The drive is still usable, but it's far from industry-leading when it comes to low queue depth read speeds. Admittedly it is industry-leading in write performance even in mainstream workloads, but the combination of the two is really what's missing. As we demonstrated with our copy test, the Vertex 4 is able to deliver good real world read performance but as our Light Storage Bench suite shows the read performance isn't consistently high. It's a frustrating dynamic, one that I truly hope is mitigated with the next firmware release as OCZ has promised.

Idle power consumption is also a concern of mine. As it stands, consuming over 1W when doing nothing isn't ok for a notebook drive. OCZ tells us a fix is on the way for this as well, but someone buying today needs to keep this in mind if it's going into a portable. The impact to overall battery life shouldn't be tremendous, but if you're on a quest to squeeze every last minute out of a single charge you may want to consider some of the alternatives.

Validation is and has always been a hot topic with every new SSD. OCZ is taking things more seriously and more importantly, has better access to fix bugs as they come up. With direct access to the firmware source code (a benefit of owning Indilinx), OCZ shouldn't have the same limits it has had in the past when working with third party controller vendors. The presumption is that now, if bugs come up in the field or during testing, they can be addressed as quickly as the Indilinx firmware engineers can type out a workaround. It remains to be seen how this works in practice, but the concept is at least sound.

In the end, as with most brand new controllers and SSD reviews our conclusion is to wait. Vertex 4 is a unique drive that really delivers a lot of what we've been asking for from a performance standpoint, but with some tangible caveats that we're told will be resolved in the coming weeks. If you're buying an SSD today, our standarding recommendation (particularly for Mac users) is Samsung's SSD 830. If you have a workload that demands better write and/or random read performance, let's see how this and other soon-to-be-announced drives behave over time before jumping the gun.

Power Consumption
Comments Locked

127 Comments

View All Comments

  • Kristian Vättö - Wednesday, April 4, 2012 - link

    240GB Vertex 3 is actually faster than 480GB Vertex 3:

    http://www.anandtech.com/bench/Product/352?vs=561
    http://www.ocztechnology.com/res/manuals/OCZ_Verte...
  • MarkLuvsCS - Wednesday, April 4, 2012 - link

    256gb and 512gb should perform nearly identical because they have the same number of NAND packages - 16. the 512gb version just uses 32gb vs 16gb NAND in the 256gb version. The differences between the 256 and 512 gb drives are negligible.
  • Iketh - Wednesday, April 4, 2012 - link

    that concept of yours depends entirely on how each line of SSD is architected... it goes without saying that each manufacturer implements different architectures....

    your comment is what is misleading
  • Glock24 - Wednesday, April 4, 2012 - link

    "...a single TRIM pass is able to restore performance to new"

    I've seen statements similar to this on previous reviews, but how do you force a TRIM pass? Do you use a third party application? Is there a console command?
  • Kristian Vättö - Wednesday, April 4, 2012 - link

    Just format the drive using Windows' Disk Management :-)
  • Glock24 - Wednesday, April 4, 2012 - link

    Well, I will ask this another way:

    Is there a way to force the TRIM command that wil nor destroy the data in the drive?
  • Kristian Vättö - Wednesday, April 4, 2012 - link

    If you've had TRIM enabled throughout the life of the drive, then there is no need to TRIM it as the empty space should already be TRIM'ed.

    One way of forcing it would be to multiply a big file (e.g. an archive or movie file) until the drive runs out of space. Then delete the multiples.
  • PartEleven - Wednesday, April 4, 2012 - link

    I was also curious about this, and hope you can clarify some more. So my understanding is that Windows 7 has TRIM enabled by default if you have an SSD right? So are you saying that if you have TRIM enable throughout the life of the drive, Windows should automagically TRIM the empty space regularly?
  • adamantinepiggy - Wednesday, April 4, 2012 - link

    http://ssd.windows98.co.uk/downloads/ssdtool.exe

    This tool will initiate a trim manually. Problem is that unless you can monitor the SSD, you won't know it has actually done anything. I know it works with Crucial Drives on Win7 as I can see the SSD's initiate a trim from the monitoring port of the SSD when I use this app. I can only "assume" it works on other SSD's too but since I can't monitor them, I can't know for sure.
  • Glock24 - Wednesday, April 4, 2012 - link

    I'll try that tool.

    For those using Linux, I've used a tool bundled with hdparm calles wiper.sh:

    wiper.sh: Linux SATA SSD TRIM utility, version 3.4, by Mark Lord.

    Linux tune-up (TRIM) utility for SATA SSDs
    Usage: /usr/sbin/wiper.sh [--max-ranges <num>] [--verbose] [--commit] <mount_point|block_device>
    Eg: /usr/sbin/wiper.sh /dev/sda1

Log in

Don't have an account? Sign up now