News for hackers. Stuff that matters.
Re:Google: Taming The Long Latency Tail - When More Machines... by littledanehren on Monday March 12, 2012 @01:17PM (#3694400)
Note: This is my own opinion, and not that of my employer (Google) or based on trade secrets or other IP from my employer.

Keeping pre-erased blocks is useful, but it can only reduce the write latency to what the chip gives you. And the chip gives you a longer write latency than read latency, especially for MLC with smaller process sizes.

Re:Google: Taming The Long Latency Tail - When More Machines... by ori_b on Monday March 12, 2012 @01:34PM (#3694478)
True, there is a difference between read and write latency, but at least that is consistent and therefore easy to plan for. Large variance makes things far more difficult, in my opinion.
Re:Google: Taming The Long Latency Tail - When More Machines... by mvgoogler on Monday March 12, 2012 @08:21PM (#3696373)
It's actually not consistent. On MLC flash, individual write operations can vary by a factor of 6.

see: http://cmrr-star.ucsd.edu/starpapers/309-Grupp-1.pdf (PDF)