Last year was dominated by two SSD controller manufacturers: Intel and Indilinx. Intel delivered the performance while Indilinx offered a value alternative. Once SandForce hit early this year however, it was game over for Indilinx. We have reviewed a couple of Indilinx drives since SandForce hit but for the most part we've been enamored with SF and Crucial's offerings.

Over the summer Indilinx was supposed to have its next-generation controller ready for debut, codenamed Jet Stream. Unfortunately the 6Gbps controller has been delayed until 2011, leaving Indilinx with two options: quietly bow out of the SSD market, or update Barefoot.

And here we have the updated Barefoot:


The Indilinx Martini based OCZ Vertex Plus

The controller is still technically called Barefoot, although it is a new hardware revision. Martini apparently refers to the firmware designed for this new rev of Barefoot (no, it can't be applied to older Barefoot drives). The Martini firmware and new Barefoot revision are designed to work better with Intel's 34nm NAND. The 3Gbps controller is designed primarily to increase random write performance although there are other benefits along the way.

Spare area has increased. While the old Barefoot set aside ~7% of the NAND capacity for garbage collection and bad block allocation, Martini uses 10%. A Barefoot+Martini based drive with 128GiB of NAND will expose 115.2GiB of it to the user vs. 119.2GiB for Barefoot based drives. SandForce once told me that it expects all controller makers to begin setting aside more spare area and that seems to be the trend.

This is the OCZ Vertex Plus, the first drive based on the Barefoot+Martini platform:

The Vertex Plus will take the place of the existing Vertex in OCZ's lineup, just below the Vertex 2 and other SandForce equipped SSDs. I asked OCZ for target pricing on the Vertex Plus when it ships in a few weeks:

OCZ's Vertex Plus Lineup
  32GB 64GB 128GB
OCZ Vertex Plus $74.99 $114.99 $194.99

A 128GB SandForce drive will set you back around $229. The Vertex Plus will save you $35. The 64GB version will be $20 cheaper than Crucial's RealSSD C300.


The back

The Vertex Plus I tested is a beta sample and is rough around the edges, which is why this is branded a Preview and not a full blown Review. Thankfully I was able to run through our entire test suite (both published and unpublished tests I use internally) on the drive. From the old Barefoot camp I've got the Corsair Nova V128, one of the last popular Indilinx based SSDs so keep an eye out for that comparison to see how Indilinx has progressed.

The Test

CPU Intel Core i7 965 running at 3.2GHz (Turbo & EIST Disabled)
Motherboard: Intel DX58SO (Intel X58)
Chipset: Intel X58 + Marvell SATA 6Gbps PCIe
Chipset Drivers: Intel 9.1.1.1015 + Intel IMSM 8.9
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 Read/Write Speed
POST A COMMENT

61 Comments

View All Comments

  • jordanclock - Tuesday, November 16, 2010 - link

    Garbage collection is file-system agnostic. It happens on a level between hardware and the file-system. It will work for any and all file-systems. Reply
  • Jaybus - Tuesday, November 16, 2010 - link

    Unlike a spinning disk, there is no penalty for where blocks are physically placed. The controller therefore maps the address of the requested block to the real physical location of the block. This mapping is internal to the drive controller and at a lower level (the block level) than the file system. When a SATA request comes in to write a block that has previously been written to and already contains data, the controller would normally have to erase the block before writing the new data. What garbage collection does is change the mapping so that the write is made to a block that is already erased, while the old block is mapped to a list of blocks that now contain stale (ie. garbage) data. The idea is that this speeds up the writes, since the erase is delayed and performed later when disk activity is idle.

    This doesn't require a TRIM command, since it is all handled internally by the drive controller. It is at the block level, so file system used doesn't matter.
    Reply
  • melgross - Tuesday, November 16, 2010 - link

    So, and I asked this before, in another thread, is there an advantage to trim. If so, what else is it doing that would make that true? I received no answer there. Reply
  • akedia - Tuesday, November 16, 2010 - link

    TRIM is a command from the operating system to the drive to clean up its dirty sectors and ready them for new data. Background garbage collection is the hard drives quietly doing the same thing by themselves when they're idle. Either way it's a process that must be undergone to keep the SSD operating well.
    The benefit of TRIM is that the operating system is much better at knowing when it's about to access the drive than the drive is at guessing when it's going to be accessed by the operating system, so TRIM can fulfill the function more efficiently and diligently. The big drawback to TRIM is that not all operating systems have it. Thus the Crucial RealSSD C300, which can receive TRIM commands but cannot do background garbage collection, is arguably the best available SSD on Windows 7, which has TRIM, but would have its performance degrade very badly over time on OS X, which does not, while the SandForce SSDs like the OCZ Vertex 2 performs about equally on either system, their own garbage collection taking care of things.
    In short, yes, there is a benefit to TRIM in keeping SSDs functioning optimally over time better than idle garbage collection most of the time, IF you have an operating system AND an SSD that utilize the command.
    Reply
  • cdillon - Tuesday, November 16, 2010 - link

    Garbage collection doesn't have ANY knowledge of file-systems like some people seem to think. That would be entirely too dangerous for your data. Block devices have absolutely no business erasing your data without the OS asking it to.

    Garbage Collection and TRIM are orthogonal. When new data is written to the SSD, it is written to the pre-erased blocks that exist in the spare block pool. The LBA for that data will now point to the new flash block. Since the contents of the logical blocks are now stored in different physical flash blocks, the old flash blocks now contain orphaned "garbage" data and can be erased and returned to the spare pool. The purpose of Garbage Collection is to erase these previously used blocks and put them back into the spare pool.

    This allows for fast writes and some wear-leveling. If you over-run the spare pool with your writes then you'll see the writes slow down until garbage collection and/or TRIM has recovered at least some of the spare block pool.

    The advantage of TRIM is that it gives the SSD information about ADDITIONAL blocks that can be erased and put into the spare pool above and beyond the fixed spare pool. The smaller the fixed spare pool size is on an SSD, the more TRIM will benefit.
    Reply
  • melgross - Wednesday, November 17, 2010 - link

    Well, this is what I thought from what I've read.

    But, it also seems to me that you can get performance at least as good as trim with controllers that are aggressive, as aggressive as the trim itself may be. We can see from the new Toshiba controller that performance can remain at about 100% if it's aggressive. Yes, that may lead to reduced life, but that's got to be tested.

    One advantage I see for garbage collection by the drive itself is that it's matched to the drivef and the extra flash should help determine how aggressive it can get. But trim is independent of the drive, as so treats each drive the same. That could result in poorer performance, and possible shorter lifetime.

    I still don't see where any advantage to trim exists.
    Reply
  • dbt - Tuesday, November 16, 2010 - link

    And.... more importantly, another good article - thankyou ! Reply
  • cactusdog - Tuesday, November 16, 2010 - link

    I have a vertex2 that im very happy with it but cant OCZ come up with a different name instead of having different controllers under the same model of "vertex" with very different performance levels. Its a good way to confuse consumers. Reply
  • Shadowmaster625 - Tuesday, November 16, 2010 - link

    I guess this is why you can buy one of the original vertexes (vertices?) for $40 after rebate. Reply
  • mschira - Tuesday, November 16, 2010 - link

    All these 2.5" SSD's are fine for desctops and for replacement in existing Laptops.
    But where is the move towards 1.8" models or better the super small form factor the MacBook air uses? (btw. does anybody know what sort of SSD the Sony Z-Series uses?)

    2.5" drives are getting a limitation for small thin notebooks. Time to get rid of them!!!!
    M.
    Reply

Log in

Don't have an account? Sign up now