Controlling Costs with no DRAM and Cheaper Flash

SandForce is a chip company. They don’t make flash, they don’t make PCBs and they definitely don’t make SSDs. As such, they want the bulk of the BOM (Bill Of Materials) cost in an SSD to go to their controllers. By writing less to the flash, there’s less data to track and smaller tables to manage on the fly. The end result is SF promises its partners that they don’t need to use any external DRAMs alongside the SF-1200 or SF-1500. It helps justify SandForce’s higher controller cost than a company like Indilinx.

By writing less to flash SandForce also believes its controllers allow SSD makers to use lower grade flash. Most MLC NAND flash on the market today is built for USB sticks or CF/SD cards. These applications have very minimal write cycle requirements. Toss some of this flash into an SSD and you’ll eventually start losing data.

Intel and other top tier SSD makers tackle this issue by using only the highest grade NAND available on the market. They take it seriously because most users don’t back up and losing your primary drive, especially when it’s supposed to be on more reliable storage, can be catastrophic.

SandForce attempts to internalize the problem in hardware, again driving up the cost/value of its controller. By simply writing less to the flash, a whole new category of cheaper MLC NAND flash can be used. In order to preserve data integrity the controller writes some redundant data to the flash. SandForce calls it similar to RAID-5, although the controller doesn’t generate parity data for every bit written. Instead there’s some element of redundancy, the extent of which SF isn’t interested in delving into at this point. The redundant data is striped across all of the flash in the SSD. SandForce believes it can correct errors at as large as the block level.

There’s ECC and CRC support in the controller as well. The controller has the ability to return correct data even if it comes back with errors from the flash. Presumably it can also mark those flash locations as bad and remember not to use them in the future.

I can’t help but believe the ability to recover corrupt data, DuraWrite technology and AES-128 encryption are somehow related. If SandForce is storing some sort of hash of the majority of data on the SSD, it’s probably not too difficult to duplicate that data, and it’s probably not all that difficult to encrypt it either. By doing the DuraWrite work up front, SandForce probably gets the rest for free (or close to it).

The Secret Sauce: 0.5x Write Amplification Capacities and Hella Overprovisioning
Comments Locked

100 Comments

View All Comments

  • Holly - Friday, January 1, 2010 - link

    Well, you can patent implementation and technology, but not the idea itself. (At least that's what my boss was trying to explain me). So, in case this idea seems worthy enough other manufacturers will come with their own MySuperStoringTechnology (c).

    Personaly I think any improvement (even if it comes out to be dead end) is worth it in global scale and this tech seems very interesting to me.

    I only have some worries about using cheaper NAND chips... Taking cheap USB flash they tend to go nuts in about 6-12 months of usage (well, I am stressing them quite a bit...) Putting them together with the best controller seems to me a bit like disbalancing things. Definitely not for servers/enthusiasts (who want the best quality for good reasons) and still too expensive for pple earning their paychecks
  • Holly - Friday, January 1, 2010 - link

    P.S. Happy New Year
  • yacoub - Thursday, December 31, 2009 - link

    I don't know that I want lower-quality Flash memory in my SSDs. I think I'd rather have both a better chip and high quality memory. But you know corners will be cut somewhere to keep the prices affordable.
  • frontliner - Thursday, December 31, 2009 - link

    Page 10 talks about Random Write in MB/s and you're talking IOPS:

    At 11K IOPS in my desktop 4KB random write test, the Vertex 2 Pro is 20% faster than Intel’s X25-M G2. Looking at it another way, the Vertex 2 Pro has 2.3x the 4KB random write performance of today’s OCZ Vertex Turbo.

    &

    Random read performance is quite good at 13K IOPS, but a little lower than Intel’s X25-M G2.
  • Anand Lal Shimpi - Thursday, December 31, 2009 - link

    woops! you're right, I decided to go with the MB/s graphs at the last minute but wrote the text based on the IOPS results. Fixed! :)

    Take care,
    Anand
  • Makaveli - Thursday, December 31, 2009 - link

    My guess is intel will release another firmware to increase the write speed on the G2 drives. As Q4 2010 is quite a long wait for a refresh. So new firmware with increase write speed and a price drop should still keep them in the driving seat.

    Kudos to OCZ for the constant shove in the back to intel tho.
  • mikesown - Thursday, December 31, 2009 - link

    Hi Anand,

    Great article! Along the subject of Intel's monopoly bullying, I was curious if you had any information about Micron manufacturing their own C300 SSDs with (very nice, it seems) Marvell controllers(see http://www.micronblogs.com/category/ssd-concepts/)">http://www.micronblogs.com/category/ssd-concepts/). I know Micron and Intel manufactured NAND jointly through their IM Flash Technologies venture, so it seems a little bit strange that Micron would manufacture competing SSDs while in a partnership with Intel. Did Intel and Micron part ways for good?

    Thanks,
    Mike
  • efficientD - Thursday, December 31, 2009 - link

    As an employee of Micron, I can say that Intel and Micron have not parted ways, but rather only had the agreement for the actual flash memory and not all of the other parts of an SSD (controller, dtc.) We are still very much in cooperation on what was agreed upon in the first place. You will notice that the OCZ in this article is Micron, and not from IM flash (the Intel/Micron joint venture). If you crack open an Intel drive, however, you will nearly exclusively find IM Flash chips along with Micron DRAM, the first gen didn't even have Micron DRAM. Hope this clarifies some things.
  • Doormat - Thursday, December 31, 2009 - link

    I'm disappointed in the lack of SATA 6Gb/s support, but a lot of that is product timing (its only now showing up in add-on chips, and controllers in late 2010/early 2011). You really wonder what the speeds are on an unbridled SF-based drive.
  • Jenoin - Thursday, December 31, 2009 - link

    "SandForce states that a full install of Windows 7 + Office 2007 results in 25GB of writes to the host, yet only 11GB of writes are passed on to the drive. In other words, 25GBs of files are written and available on the SSD, but only 11GB of flash is actually occupied. Clearly it’s not bit-for-bit data storage."
    "What SF appears to be doing is some form of real-time compression on data sent to the drive."
    Based on what they said (and what they didn't say) I have to disagree. It appears to me that they are comparing the write that is requested with the data already on the SSD and only writing to the bits that need changed thereby write amplification ~0.5. This would explain the high number of IOPS during your compressed file write test perhaps. That test would then be a mixed test of sequential and random writes giving you performance numbers in between the two other tests. Could you verify the actual disk usage with windows 7 and Office installed? If it indicates 11gb used then it is using some kind of compression but if it indicates the full size on the disk then it is using something similar to what I detailed. I just thought it interesting that Sandforce never said things would take up less space, (which would be a large selling point) they only said it would have to write about half as much supporting my theory.

Log in

Don't have an account? Sign up now