Given the short timing of this project we're just going to dive right in and get to work on this one. Just a month ago OCZ Technology released their new flagship consumer SSD, the Vertex 4. In our testing we observed a rather strange issue when reading data from the drives provided by OCZ. The issue had to do with single read requests for data, a single command. Both the 256GB and 512GB models provided to us would only read at around 200MB/s. This hampered the drives in several benchmarks and was even observed in several real-world tasks. The 200MB/s limit was surpassed when asking the drive to read two files, then up to 400MB/s. Three files read further increased the Vertex 4 performance to their maximum read limits. The ability to multitask with native command queuing (NCQ) is a great feature, but one that most consumers rarely take advantage of... we are just single task creatures, performing one step at a time.

When it comes to OCZ's house brand Indilinx, firmware changes, when needed, will be rapid. OCZ doesn't need to wait for a third party to get involved. As you know by now, Indilinx Infused at this time doesn't mean 100% Indilinx, but rather Indilinx programming and firmware sitting atop Marvell silicon. We suspected as much while testing the OCZ Octane, but without proof or a State of Solid State article between then and now, we kept our speculations to ourselves. Either way, none of this really matters because Marvell just makes the hardware and the SSD manufacturers come up with the rest. This is why every SSD based on Marvell controllers perform differently, from the Crucial C300 to the Corsair Performance 3; the changes in performance and behavior are pretty broad.