I've been following this report for many years, but Backblaze, as a backup service (traditionally), has very different IO patterns than many users. They originally started with consumer drives, which we found to be far too unreliable. In my experience, the BER and write cycles have a dramatic impact on overall drive performance. The MTBF declines sharply as write cycles increase, both as a percentage of IO and overall IO.

Backblaze changed IO patterns with B2, but that would be the key data for me to make this more useful: failure rate as a percentage of bytes read/written, etc.