3 ms·
Disclaimer: I work at Backblaze. > If they've hit on a different access pattern that is more gentle, that might be something useful for posterity and I hope th
by brianwski 6y ago
Disclaimer: I work at Backblaze.
> If they've hit on a different access pattern that is more gentle, that might be something useful for posterity and I hope they dig into that possibility.
Internally at Backblaze, we're WAY more likely to be spending time trying to figure out why drives (or something else like power supplies or power strips or any other pain point) is failing at a higher rate, than looking into why something is going well. I'm totally serious, if something is going "the same as always or getting better" it just isn't going to get much of any attention.
You have to understand that with these stats, we're just reporting on what happened in our datacenter - the outcome of our operations. We don't really have much time to do more research and there isn't much more info than what you have. And if we stumbled upon something useful we would most likely blog about it. :-)
So we read all of YOUR comments looking for the insightful gems. We're all in this together desperate for the same information.
- hinkley 6y agoSeems to me that every drive failure causes read/write amplification, so a small decrease in failure rates would compound. Have you folks done any other work to reduce write amplification this year?