> However, was dumbfounded by the lack of information on delay before check. Yes, I was wondering about this too. I examined the source code in the GitHub repo

> However, was dumbfounded by the lack of information on delay before check. Yes, I was wondering about this too. I examined the source code in the GitHub repository and found that all the follow-up operations are immediate. No consideration of or measurement of latency. > I wonder if the experiment normalizes for the client origin. Unfortunately it does not. As you imply, a high round trip time, or just high latency of the storage operations in general, could easily affect the apparent consistency with the current experiment design. In an enhanced version of this experiment I think it would be helpful to have latency measurements, such as total time from beginning of write until end of read (average and percentiles); and as you suggested round trip time measurements. Luckily the code is available, so I suppose it's on us to reproduce the results and extend them! Fortunately the code is also pretty short, since a lot of the storage system specific logic is encapsulated within the Apache JClouds library. (To clarify, I don't question the accuracy of the results they are about what I'd expect. I'm mostly being pedantic in drilling into these concerns, and wondering what more information we might be able to extract from the experiment.)