I’m all for benchmarking and showing that your product is better from a technical standpoint. But at least for me, this is not the way.
The test is relevant for users running workloads across multiple clouds, or running in neo-clouds like Coreweave, Together.ai, Lambda Labs, etc. In such cases, the storage is typically S3, or R2.
There is of course going to be additional latency when S3 is used outside the AWS network. But that is the practical case as well when using S3 in multi-cloud workloads. The same applies to R2, which is often used outside their worker product through compute that is not part of the Cloudflare network infra.
The benchmark uses standard tier for buckets, which tends to be the most common. The blog post should have mentioned the tier. A miss from my side.
What more would you have wanted to see? The benchmark is using the open source go-ycsb tool and is easily reproducible.
Is this the endpoint you tested against? https://bgp.he.net/dns/t3.storage.dev#_ipinfo
Did you test from a VM in the same cloud that's hosting the product? If so I'm not sure "neutral cloud provider" is an honest statement.
