2 ms·
The biggest thing missing from the paper seems to be SLC caching, which is now nearly universal on client SSDs but usually not used on enterprise SSDs. Modern S
by wtallis 9y ago
The biggest thing missing from the paper seems to be SLC caching, which is now nearly universal on client SSDs but usually not used on enterprise SSDs. Modern SSDs also use much more robust error correction schemes than they did 5 years ago; almost everything has LDPC soft-decode or similar as a fallback, which gives an effective increase in the write endurance of the drive.
There are also trends underway to dismantle some of the abstractions between the file system and the flash. Even when a SSD is presenting an interface of 512B or 4kB logical blocks for compatibility reasons, it can inform the host of the optimal block size to use for I/O. The host can also tag I/O commands with a stream ID, allowing the SSD to store related data together and separate from unrelated streams. Used properly, this approximates generational garbage collection and improves both performance and write amplification.
There's also a recently standardized feature for partitioning a SSD in a way that makes hard guarantees about the sharing (or lack thereof) of memory channels and flash chips. This is intended primarily for multi-tenant use cases, to ensure that one process/VM's I/O won't inflict garbage collection pauses upon another process/VM. In a similar vein, there are now mechanisms to request that the SSD defer all background processing for a while in order to service a burst of I/O with minimal and predictable latency, and controls for whether a SSD is permitted to do non-critical background processing during idle time (you may not want that happening while running on battery).
Beyond that, there's some work on open-channel SSDs that move large portions of the flash translation layer to the host system, allowing all the above controls and more to be managed by the host. With application-layer tuning this can be extremely powerful.