Last week OCZ pulled the trigger and introduced the world’s first SF-2000 based SSD: the Vertex 3 Pro. Not only was it the world’s first drive to use SandForce’s 2nd generation SSD controller, the Vertex 3 Pro was also the first SATA drive we’ve tested to be able to break 500MB/s on both reads and writes. Granted that’s with highly compressible data but the figures are impressive nonetheless. What wasn’t impressive however was the price. The Vertex 3 Pro is an enterprise class drive, complete with features that aren’t exactly in high demand on a desktop. As a result the V3P commands a premium - the drive starts at $525 for a 100GB capacity.

Just as we saw last round however, if there’s a Vertex 3 Pro, there’s bound to be a more reasonably priced non-Pro version without some of the enterprisey features. Indeed there is. Contained within this nondescript housing is the first beta of OCZ’s Vertex 3 based on a SandForce SF-2200 series controller. The price point? Less than half of that of the V3P:

Pricing Comparison
  128GB 256GB 512GB
OCZ Vertex 3 Pro $525 (100GB) $775 (200GB) $1350 (400GB)
OCZ Vertex 3 $249.99 $499.99 N/A

At an estimated $250 for a 120GB drive the Vertex 3 is more expensive than today’s Vertex 2, but not by too much nor do I expect that price premium to last for long. The Vertex 2 is on its way out and will ultimately be replaced by the V3. And SSD prices will continue to fall.

What sets a Vertex 3 apart from a Vertex 3 Pro? Not all that much, but SandForce has grown a lot in the past year and instead of just a couple of SKUs this time around there are no less than seven members of the SF-2000 family.

You should first know that SandForce only produces a single die, the differences between all of the members of the SF-2000 family are strictly packaging, firmware and testing.

The main categories here are SF-2100, SF-2200, SF-2500 and SF-2600. The 2500/2600 parts are focused on the enterprise. They’re put through more aggressive testing, their firmware supports enterprise specific features and they support the use of a supercap to minimize dataloss in the event of a power failure. The difference between the SF-2582 and the SF-2682 boils down to one feature: support for non-512B sectors. Whether or not you need support for this really depends on the type of system it’s going into. Some SANs demand non-512B sectors in which case the SF-2682 is the right choice.

You may remember that our Vertex 3 Pro sample used a SF-2682 controller. That’s because initially all SandForce made were SF-2682s. Final versions of the V3P will likely use the cheaper SF-2582.

The SF-2200/2100 series are more interesting because of their lower target price points. You lose support for the supercap but that’s not as big of a deal on the desktop since you’re not working with mission critical data. The big difference between the 2200 and 2100 is support for 6Gbps SATA, the former supports it while the latter doesn’t. This is a pretty big difference because as we’ve seen, when paired with a 3Gbps controller the SF-2000 isn’t too much better than what we had with the SF-1000.

The other big difference is the number of byte lanes supported by the controller. The SF-2181 and above all support 8 NAND flash channels, however only the SF-2282 supports 16 byte lanes. Each NAND device is 8 bytes wide, supporting 16 byte lanes means that each channel can be populated by two NAND devices. This lets a single SF-2282 controller talk to twice as many NAND devices as a SF-2281.

There’s no performance difference between the 8 and 16-byte lane versions of the chip, it’s just a matter of pure capacity. Thankfully with 25nm NAND you can get 8GB of MLC NAND on a single die so both the 2281 and 2282 should be able to hit 512GB capacities (the 2281 simply needs higher density NAND packages).

The Vertex 3 sample we have here today uses the SF-2281. Our sample came configured with sixteen 16GB Micron 25nm ONFI 2.0 NAND devices. Remember that while both Intel and Micron own the 25nm fabs, the two companies are providing different specs/yields on 25nm NAND. The 25nm Micron stuff is rated at around 3,000 p/e cycles from what I’ve heard, while the Intel 25nm is rated at 5,000. The main difference here is that the Micron is available in great quantities today while the Intel 25nm isn’t.

RAISE: Optional

One other difference between the SF-2500/2600 and the SF-2100/2200 is the optional nature of RAISE. You'll remember that in order to allow for lower quality NAND SandForce stripes a small amount of redundant data across the array of NAND in a SF-1000/2000 drive. SandForce never stores your actual data, rather a smaller hash/representation of your data. When your data is compressed/deduped for storage, SandForce's controller also generates parity data equal to the size of a single NAND die in the array. This process is known as RAISE (Redundant Array of Independent Silicon Elements) and it allows you to lose as much as a full NAND die worth of data and still never see a bit of data loss from the user's standpoint. At 25nm however a single die can be as large as 8GB, which on a lower capacity drive can be a significant percentage of the total drive capacity.

With the SF-2100/2200, SandForce allows the manufacturer to disable RAISE entirely. At that point you're left with the new 55-bit BCH ECC engine to do any error correcting. According to SandForce the new BCH ECC engine is sufficient for dealing with errors you'd see on 25nm NAND and RAISE isn't necessary for desktop workloads. Drive makers are currently contemplating what to do with RAISE but as of now the Vertex 3 is set to ship with it enabled. The drive we have here today has 256GB of NAND, it'll be advertised as a 240GB drive and appear as a 223.5GB drive in Windows.

Here We Go Again: 4KB Random Write IOP Caps

With the SF-1200 SandForce capped the peak 4KB random write speed of certain drives while negotiating exclusive special firmware deals with other companies to enable higher performance. It was all very confusing as SandForce shipped initial firmware revisions with higher performance and later attempted to take that performance away through later firmware updates.

If you pay attention to the table above you’ll notice that there are two specs for 4KB random write IOPS: burst and sustained. The burst value is for around 15 seconds of operation, the sustained is what happens when the firmware initiated performance cap kicks into action. By default the SF-2100/2200 drives have a cap of 20,000 IOPS for 4KB random writes. After a period of about 15 seconds, the max performance on these drives will drop to 20K. The SF-2500/2600 controllers are uncapped, max performance can remain at up to 60K IOPS.

The beta Vertex 3 review sample I have here today manages around 45K IOPS in our 4KB random write test. That test runs for 3 minutes straight so obviously the cap should’ve kicked in. However it didn’t.

I asked SandForce why this was. SandForce told me that the initial pre-release firmwares on the SF-2200 drives don’t have the cap enabled, but the final release will put the cap in place. I also asked SandForce if it was possible for one of its partners to ship with a special firmware build that didn’t have the cap in place. SandForce replied that anything was possible.

I asked OCZ if this meant the drive I was testing wasn’t representative of final, shipping performance. OCZ stated very clearly that performance will not change between the drive I have today and the drive that goes on sale in the next 2 months. To me this sounds like SF and OCZ have struck another exclusive firmware deal to ensure slightly higher performance on the Vertex 3 compared to a standard SF-2200 based drive.

SandForce wouldn’t comment on any existing agreements and OCZ said it couldn’t get SandForce to confirm that the V3’s performance wouldn’t change between now and its eventual release. Based on what we saw last time I expect SandForce to offer the 60K IOPS firmware to all partners that meet certain order size commitments. Order enough controllers and you get a special firmware, otherwise you’re stuck with the stock SF-2200 firmware.

Of course this makes things very confusing for those of you looking to shop around when buying a SF-2200 drive. I do wish SandForce would just stick to a single spec and not play these sorts of games but that’s just how business works unfortunately.

The good news is that for most desktop workloads you don’t really benefit from being able to execute more than 20K IOPS, at least in today’s usage models.

Faster than a Vertex 3 Pro & The Test
POST A COMMENT

85 Comments

View All Comments

  • swaaye - Thursday, February 24, 2011 - link

    It'll depend on how fast your CPU is because it will become the bottleneck if it's not already. Reply
  • Mumrik - Thursday, February 24, 2011 - link

    "Order enough controllers and you get a special firmware, otherwise you’re stuck with the stock SF-2200 firmware.
    (...)I do wish SandForce would just stick to a single spec and not play these sorts of games but that’s just how business works unfortunately."

    Is it really? I've never heard of anything similar elsewhere in the storage space. This really sounds to me like the kind of thing you should keep pushing them on Anand....
    Reply
  • taltamir - Thursday, February 24, 2011 - link

    so... 7 "models" which are the exact same chip with different firmware / different configuration (supercap, amount of NAND, etc)
    And even within those so called "models" there is different levels of performance capping in firmware due to various exclusivity contracts which are not actually being reported or represented in the chip's name?

    I am liking sandforce less and less.
    Reply
  • TGressus - Thursday, February 24, 2011 - link

    +1

    It's even more egregious when vendors are sending the reviewers pre-release samples that may or may not represent the final retail product.
    Reply
  • taltamir - Thursday, February 24, 2011 - link

    you are correct, that does make it even worse. Reply
  • jaydee - Thursday, February 24, 2011 - link

    Interesting read from a theoretical perspective, but it would be far more useful for your readership to have a roundup involving 60-120GB SSD's. I can find benchmarks on budget video cards, cpu's, and read reviews on budget motherboards. I do realize there are no 60-120GB Vertex 3's available, but 6-9 months after launch I still have no idea how (for instance) the Sandforce, JMicron, Samsung, Indillinx, Marvell, Intel, Toshiba 60-90GB SSD's benchmark against each other considering they all scale down differently from the 240GB models which are often reviewed.

    240GB SSD's are neat, but not affordable for many.
    Reply
  • 86waterpumper - Thursday, February 24, 2011 - link

    I agree, the 128gb size seems to be the sweet spot, that is what I've decided to go with, just not sure
    whether it will be the newest sandforce or the c400. I wish we could get some testing on the amd
    motherboard controllers too. I know intel is more popular right now but amd is still a viable option
    for many. I would think this is especially important since amd finally released a ahci driver not too
    long ago, but I haven't heard much about how good it is.
    Reply
  • ol1bit - Thursday, February 24, 2011 - link

    I can't believe the jump, Intel better be on their game or they might find themselves without a market anymore.

    My Intel 80gb is old after 1.5 years! LOL
    Reply
  • seapeople - Thursday, February 24, 2011 - link

    Sell an x25m g2 for $1.5/GB and they are right back on top of the value/money game. Especially when you consider issues like reliability reputation versus these new drives. I wonder what the profit margin on these drives are... There might be a lot of leeway to drop price to capture market on these, considering their "real" competitors are HD's. Reply
  • boxleitnerb - Thursday, February 24, 2011 - link

    Hey Anand,

    I was wondering if you're considering writing about the CPU-SSD dynamic in a future article. As I understand it, the SSDs can serve requests so fast that in some scenarios the CPU again becomes the limiting factor.

    I would be especially interested in common tasks like virus scanning, gaming/application load times/installation and windows startup. I know this could be alot of work, so maybe you can pick only one or two of these tasks and analyze them with CPUs with a different number of cores and clock speeds.

    What do you think about it?
    Reply

Log in

Don't have an account? Sign up now