Slashdot Mirror
Micron Releases 16nm-Process SSDs With Dynamic Flash Programming
Lucas123 writes: Micron's newest client flash drive line, the M600, uses its first 16nm process technology and dynamic write acceleration firmware that allows the flash to be programmed as SLC or MLC instead of using overprovisioning or reserving a permanent pool of flash cache to accelerate writes. The ability to dynamically program the flash reduces power use and improves write performance as much as 2.8 times over models without the feature, according to Jon Tanguy, Micron's senior technical marketing engineer. The new lithography process technology also allowed Micron to reduce the price of the flash drive to 45 cents a gigabyte.
Seems like the durability of flash cells decreases with every process shrink. It makes me wonder what the lifetime of this new stuff will be. A 10% reduction in cost is no bargain if it comes with a 10% reduction in lifetime.
Making assumptions about how often trim might be used for any given workload only obscures the actual write endurance. Much like a 100GB capacity tape that's marked as 200GB because dome data that the manufacturer chose compressed 2:1 before being sent to the tape drive. Your mpeg movies aren't going to compress, so you'll be able to put 100GB of movies on that 100GB tape. The 200GB number is pure marketing BS.
At least with tapes, all if the companies use the same 2:1 bs factor, so they can be compared. There's no telling what assumptions Micron made about the use of trim, so there's no way to compare this drive's endurance to any other, or to estimate it's actual endurance for any real workload.
It sounds like you're saying /. doesn't support Unicode. Make all the excuses you want about it being hard -- they might be true -- but Unicode support on /. does not exist. The idea that a whitelist (that doesn't even include mu) is evidence of support is like claiming that an F1 car is road-legal because you added headlights.
Theres a lot of misconception here, so I'll try to address them.
Making assumptions about how often trim might be used for any given workload only obscures the actual write endurance.
TRIM has nothing to do with endurance. TRIM erases cells that are scheduled for erasure anyways; all TRIM does is try to time that erasure such that it occurs at a time that will not effect performance. What affects endurance is wear leveling, which is an entirely separate technique that does actually work. As capacity increases, wear-leveling ensures that the endurance of the drive as a total increases.
Much like a 100GB capacity tape that's marked as 200GB because dome data that the manufacturer chose compressed 2:1 before being sent to the tape drive. Your mpeg movies aren't going to compress, so you'll be able to put 100GB of movies on that 100GB tape. The 200GB number is pure marketing BS.
When tape manufacturers (or organizations, like the one behind LTO) cite a compression factor like 2:1, it is based on a standard body of data like the calgary corpus which includes both compressible and uncompressible data. This allows you to compare different technologies with different compression standards.
In the real world on LTO (which I assume you are referring to) I have seen compression factors ranging from ~1.5 to 2.5, so its not really accurate to call it marketing BS. They also always (as far as I have seen) mark the tapes something like "800GB/1600GB" with the subtext explaining that the smaller number is native, and that the entire thing is 2:1. Its not dishonest because the compression is part of the (well-defined) standard, and the native capacity is right next to the compressed capacity. Its also not the manufacturer doing this; those numbers are explicitly defined in the spec.
all if the companies use the same 2:1 bs factor,
Which begins to make sense when you realize that thats because LTO itself defines the compression factor of 2:1 based on calgary corpus.
There's no telling what assumptions Micron made about the use of trim
But, as we've established, TRIM has literally no effect on endurance, so its irrelevant what they might assume about it.
so there's no way to compare this drive's endurance to any other, or to estimate it's actual endurance for any real workload.
Not to be harsh, but there is if you actually took the time to understand the tech. They usually do provide endurance stats (ie, "100PB data endurance") and tests by Anandtech and others have often validated that as being realistic.