Slashdot Mirror
NAND Flash Better Than DRAM For PC Performance
Lucas123 writes "Adding NAND flash memory to a PC does more for performance than DRAM and costs less, according to a new study. As the price difference between the two memory types widens, NAND flash will become the memory of choice in the PC. The effects of NAND flash adoption are already being felt in the DRAM market, as revenue in 2011 is expected to decline 11.8%."
Compact flash cards, SD cards, SSD, USB sticks all see this problem. So far we've only found a few suppliers of Compact flash cards which guarantee the internal management is safe, and we tested it and found it to be true. SD cards, I've a few broken "industrial grade" SD cards on my desk as proof that this is not the case. SSD is to large for our product, so I have no tests for these, but I expect the problem to be the same.
If you expect SSDs to have exactly the same problems as SD cards, you're a total moron with at best shallow expertise in the field. Go look up the specs of controller ICs used in SSDs and try to tell me with a straight face that they're exactly the same thing you'd get in a SD card, or even a very good CF card.
To pick just one example, do you know of any CF cards which compress all data on the fly in order to increase effective flash lifespan by reducing the total amount of data written? (Since the SSD controllers in question use hardware compression engines which can handle hundreds of megabytes per second throughput, this also has the nice side effect of increasing effective performance, unless you're storing incompressible data.)
We use raw flash, with linux and JFFS2 or UBIFS. Which is a filesystem designed to run on flash, raw flash. Wake me when "SSD" offers that solution.
Whatever makes you think the FTL (flash translation layer) firmware inside SSDs isn't designed to run on flash, raw flash? Whatever makes you think that a generic one-size-fits-all software solution like JFFS2 applied to whatever random flash memory you put in your embedded system is better than a SSD whose firmware has been tuned for the specific flash chips it was built with? (One of the fun things about NAND flash is that it's far from generic, especially MLC, and even more especially sub-30nm MLC NAND.)
More broadly, JFFS2 is one way to skin the cat, having a "drive" abstract flash into a generic block device is another. If you want low cost, low-to-medium performance, and probably not the best possible reliability, especially for heavy write loads, JFFS2 and friends will do just fine. If you want a real HDD replacement for non-embedded-systems, it's not even close to being the right solution. Which is why you don't see anybody trying to deploy flash-managing filesystems as HDD replacements.
The controllers used in real SSDs are expensive enough that it would be a huge win if you could toss them and just use a flash FS. There are lots of very good reasons why this has not happened and will not happen. Take your head out of your butt and get some perspective, right now you're a classic example of how a little knowledge is a dangerous thing.
(TRIM is not a sollution, it's a workaround)
No, TRIM is an attempt to improve performance which has been oversold a bit in the popular computer press.