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.

The Test


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


Intel DX58SO (Intel X58)

Intel H67 Motherboard


Intel X58 + Marvell SATA 6Gbps PCIe

Intel H67
Chipset Drivers:

Intel + Intel IMSM 8.9

Intel + 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


Random & Sequential Read/Write Speed
Comments Locked


View All Comments

  • GullLars - Thursday, June 30, 2011 - link

    This card will get decimated by even an 80GB ioDrive, not to mention the 320GB ioDrive Duo, in just about any real world scenario. They are designed from completely different standpoints.

    While both are highly parallell, the ioDrive is highly optimized for latency and can push close to 20.000 4KB random read IOPS (~75-80MB/s) at a QD of 1, while Revodrive 3 x2 reaches 13K at QD 3, and around 4-5K at QD 1.
    The ioDrive also handles mixed IO well, and scales really fast at low block sizes and queue depths, so you would need incredibly heavy parallell workloads to keep it at a notable QD (>10).

    What bothers me the most with the Revodrive 3 x2 is that it doesn't implement an onboard cache at all. With 64-512MB you could use it for read-ahead and hit those GB/s+ seq bandwidth numbers at a QD of 1 for fairly small block sizes.
    With a (super?)capacitor you could also safely use say 8-16MB of that cache for write buffering and saturate the array.
  • GullLars - Thursday, June 30, 2011 - link

    Correction, RevoDrive 3 x2 benched 7K 4KB random read IOPS @ QD 1 in AS SSD.
  • Jharne - Tuesday, June 28, 2011 - link

    The INF mentions VEN_11AB & VEN_1B4B which are both Marvell. So I'm guessing they built the controller.
  • DigitalFreak - Tuesday, June 28, 2011 - link

    LOL. All the trouble they go through to hide the controller vendor and all you need to do is look at the vendor ID
  • VStrom - Tuesday, June 28, 2011 - link

    You can boot with this on x64 with an unsigned just need to load Windows with the signed driver validation disabled (F8 before Windows loads).
  • DanNeely - Tuesday, June 28, 2011 - link

    If you need to do this before every boot it's a non-option in the server world. In normal operation no keyboard/mouse/monitor will be attached, all interaction will be via remote desktop type services after it's booted.
  • VStrom - Tuesday, June 28, 2011 - link

    True, but I was referring to Andand's comment specifically about Win 7 saying "Windows 7 x64 won't boot off of the RevoDrive 3". When this ships, the driver will be ready and a non-issue for servers.
  • bacomatic - Tuesday, September 13, 2011 - link

    Apparently this has been fixed, I am booting Win 7 x64 from this drive with the current drivers.
  • quiksilvr - Tuesday, June 28, 2011 - link

    I would have figured with this strong staple in the 2.5" SSD market with TRIM enabled devices this would not be hard to to.
  • mikeblas - Tuesday, June 28, 2011 - link

    Comparing this device against consumer-level SSDs seems like a waste of time. Why not compare against fusionio?

    I'd also like to see a benchmark that runs for a sustained period. The problem with SSD is the ability to keep up with write loads. If you run the 4K random IO benchmark for 48 hours, does the IOPS rate spike or trend downwards, or does it stay flat? The write ratio of your benchmark is around 33%, which I don't think represents OLTP applications too well.

    The review doesn't comment on the stability of the drivers, their memory usage on the host, or the management and monitoring tools for the drive. Do I get a tool that measures remaps, does SNMP, or email alerting?

Log in

Don't have an account? Sign up now