Thanks, but I disagree with the approach of only showing storage benchmarks with disabled caches. Production workloads will encounter variance between the providers thanks to different caches and behaviors of handling direct I/O. I'd include direct I/O results _with_ cached results, so that I wasn't misleading my customers.

I know what I'm suggesting is not the current norm for cloud evaluations. And I believe the current norm is wrong.

The more important question is how the benchmarks were analyzed -- what other tools were run to confirm that they measured what they were supposed to?