Although consumer SSDs are far from a mature technology, PCIe SSDs are even further behind on the growth curve. The upside is huge. As SandForce has already demonstrated with the right dataset a single SSD can nearly saturate the 6Gbps SATA bus. Rather than force OEMs into putting yet another very high bandwidth bus on the motherboard, SSD vendors everywhere (Intel included) turn their attention to PCIe as a solution to the problem.

The holy grail is a native PCIe solution. Recently Micron announced such a thing: the P320h. However the estimated price tag on the P320h could be in the $5000 - $10000 range depending on capacity.

Manufacturers in the consumer SSD space are attracted to PCIe solutions simply because margins are higher. For the most part, client storage is a commodity and if you don't make the NAND and controller going into an SSD you're not making a ton of money selling drives to end users. Sell to an enterprise customer and all of the sudden a couple thousand dollars per drive seems like a bargain.

The original RevoDrive

OCZ started making PCIe SSDs the simplest way possible. Take a couple of SSDs, put them on a single PCB behind an on-board RAID controller and you're good to go. The single card performance was decent but of course there were issues. A single controller failure would take out the whole drive and things like TRIM weren't supported either.

The RevoDrive X2

Recently OCZ has been trying very hard to be more than just a rebrander of components. The acquisition of Indilinx puts a wedge between OCZ and a lot of its former peers in the memory business, but it's still a far cry from Intel or Samsung. Its latest PCIe SSD is another step in the maturing of the company. This is the RevoDrive 3 X2:

The RevoDrive 3 X2

Like previous RevoDrives, the third edition places two SSD controllers (and their associated NAND) on a single PCB. The X2 suffix denotes the two PCBs in use on this particular design. Unlike previous RevoDrives however, the RevoDrive 3 doesn't use a kludgy SATA-to-PCI-X-to-PCIe chain. Instead this drive has a single chip that acts as a 4-port 6Gbps SAS to PCIe x4 (gen2) bridge.

Right off the bat that gives the RevoDrive 3 a full 2GB/s of bandwidth to your system, assuming you've got a x4 (or wider) port available. The RevoDrive 3, like many PCIe devices, will work in x8 and x16 slots as well.

As you'd expect, the RevoDrive 3 uses SandForce's latest SF-2281 controllers. The drive will be available in dual and quad SF-2281 configurations, with capacities ranging from 120GB all the way up to 960GB. Prices and configurations are below:

OCZ RevoDrive 3 Lineup

Number of PCBs

Number of Controllers

Price

OCZ RevoDrive 3 120GB

1

2

$399.99

OCZ RevoDrive 3 240GB

1

2

$599.99

OCZ RevoDrive 3 480GB

1

2

$1499.99

OCZ RevoDrive 3 X2 480GB

2

4

$1699.99

OCZ RevoDrive 3 X2 960GB

2

4

$3199.99

OCZ isn't revealing the manufacturer of the SAS controller and even went as far as to silkscreen its own logo and part number on the chip. OCZ's efforts are understandable because it claims that the manufacturer of the controller allowed OCZ to modify the firmware and driver of the controller, to customize it to the specific needs of the RevoDrive 3.

Even a look at the RevoDrive 3's driver INF file reveals no indication of the chip's OEM (Update: As a number of you have pointed out, the vendor ID seems to indicate that OCZ is using a Marvell SAS controller as the base for the RevoDrive 3):

OCZ calls this chip its SuperScale storage controller.

VCA 2.0

OCZ wanted to address key limitations of previous RevoDrives: the ability to TRIM and receive SMART data from the drive. The former helps keep performance high while the later is important for users concerned about the health of their drive. Customizing the RevoDrive's controller was the only way to ensure these commands were properly passed. OCZ calls this its Virtualized Controller Architecture 2.0.

The RevoDrive 3's controller is a standard SAS RAID device, however unlike typical RAID-0 arrays data isn't striped across all controllers on the card. Instead OCZ claims its driver accumulates IO queues and dispatches individual IO requests to available SSD controllers. In theory, OCZ's approach wouldn't require matching stripe size to workload - all you need is tons of parallel IO and the software/firmware should take care of the rest. OCZ tells me it has special allowances for corner cases to make sure that one controller isn't writing proportionally more data to its NAND than the others in the system.

The RevoDrive 3 currently has WHQL driver support for 32-bit Windows 7 and non-WHQL support for 64-bit Windows 7. OCZ is working on WHQL certification for its 64-bit driver but that wasn't available to us at the time of this review.

Unfortunately without WHQL certification on the 64-bit driver that means Windows 7 x64 won't boot off of the RevoDrive 3. The 32-bit version will and OCZ expects both versions of Windows to be bootable by the end of July when the drive is available. This is an important feature as OCZ is touting the drive's ability to function as a boot device as a key feature.

RevoDrive 3 X2 - main PCB

RevoDrive 3 X2 - daughterboard

The other major problem with the RevoDrive 3, and unfortunately one that won't be solved in the near future is that although the drive supports TRIM - Windows 7 won't pass the command to the drive. Apparently this is a current limitation that impacts all SCSI/SAS controllers and it's something that only Microsoft can fix. I asked OCZ what the likelihood was that Microsoft would fix this in the near term. OCZ believes that for the next version of Windows Server it's a problem that will have to be addressed, however I didn't get a clear answer on if we can expect anything between now and then.

Unlike the RevoDrive 2 however, you can secure erase the RevoDrive 3 using OCZ's SandForce Toolbox. Unfortunately any hopes for real time TRIM support are thrown out the window until Microsoft decides to update Windows.

OCZ did mention that the upcoming z-Drive would have Linux support with fully functional TRIM. Under Windows however if you send a TRIM command to a SCSI/SAS controller the command just gets thrown away before it ever hits the driver.

Post Your Comment

38 Comments

You can do secure erase, is there any sort of garbage cleanup tool they also supply for maintenance? I know Intel supplies these with their SSDs for if TRIM is unavailable, and that seems like something which you ought to have to make up for this shortcoming.

It's a shame OCZ started you all off with such an expensive offering. I'd be far more interested in the performance of the Revodrive 3 (no x2) 120gb or 240gb.Reply

I started reading this review, saw the specs and that they removed the pci-x bridge and said to myself "This thing is gonna hit 2GB/s sequential." Close.

Man is this thing fast. It is very interesting especially on a enterprise environment and that is due to the data workload, nothing else.

I personally have been running the original 120GB Revodrive (2 Sandforce 1200 controllers) and I've had absolutely zero reliability issues in 24x7 running on a linux box that is my personal workstation. Bought September 2010 so almost a year old now. I'd call that 'good', so far. Tentatively.

So what is the driver used for this under Linux? Is there one? If Ocz have made changes to firmware then they need to release a driver for linux no?Reply

Dear Anand,first off all for doing what you do her. I have learned so much from your SSD (and other technology coverage).

As you really have this powerful voice in the industry and have always used it in favor of the users and consumers I'd like you to shed more light on supported platforms of SSDs as part of your reviews and tests.

I have at work a Mac Pro with a couple of 120GB OCZ Vertex SSDs which got corrupted by a power outage Monday morning. Not a big deal as the data on them was of temporary nature.

However, my attempt to use that opportunity and secure erase the drives and may be update the firmware failed miserably:* OCZ does not make it easy to find the tools* OCZ makes you download a package for all platforms which then you have to select (w/o a guide) the "right" model and burn the tools on a CD* The Insturctions require to set BIOS modes for ATAPI, so are PC only* The required BIOS mode (IDE) is again PC only* Finally I had to use PC Laptop to to boot the CD and it painfully failed to boot because of some CD driver for the CD drive missing.

So to actually restore the drive to factory conditions one needs to have some very specific hardware (if it works at all then, never got to that point).

In my book this is clearly poor customer support and platform support. I'd like to see more details about the actually supported platforms for this new technology including the secure erase tooling (or other tooling that OCZ does provide, like some form of garbage collection tool).Reply

1) All the benchmarks are for desktop apps. I really doubt people would be buying PCIe SSD for "Starcraft II & WoW" (!!) Far more likely people would be using it for MySQL, Solr, Hadoop, VM. Can we get a benchmark based on those apps?

2) You only tested random read at low queue depth and simply concluded that "Low queue depth random read performance is nothing to be impressed by." What about high queue depth? Random read IO at high concurrency and high queue depth is just about the *MOST* important metrics for server SSD uses -- yes even more important than random write IO. Yet you completely skip over that. Any chance you can update the benchmark to include results at high concurrency and high queue depth?Reply

I really really really would like to see some server testing done with server class devices. Specifically I'd like to see the testing done on a modern *nix kernel, as this type of device will likely see usage in this environment.Reply