You write that reads will not trigger wear leveling, and then you go on to explain multiple scenarios in which reads will trigger rewrites. Those rewrites can c

You write that reads will not trigger wear leveling, and then you go on to explain multiple scenarios in which reads will trigger rewrites. Those rewrites can cause elevated read latency. I have done SSD code reviews with multiple SSD vendors, and there are some which will trigger wear leveling after a set number of reads, instead of waiting for elevated bit error rates. And yes, the elevated read latency should be in the order of 5ms, which shouldn’t impact a properly buffered audio application, but the world is full of incorrectly designed applications. https://storageswiss.com/2019/04/18/not-achieving-the-ssd-performance-you-expected-latency/amp/ https://storageswiss.com/2019/04/18/not-achieving-the-ssd-pe... As for enterprise drives, there are dozens of tricks to ensure lower latency. Reading from other members in an erasure code, read prioritization over writes. It all depends upon how low of latency you’re trying to achieve, and with what level of consistency. My point was that this drive may be using some innovative techniques to achieve consistently low read latencies in a “consumer” class drive. Possibly novel.