> Tested in production at scale: On AWS, response times average 100 ms for cache hits, 200 ms for misses. Cloudflare is significantly slower, but is improving as Cloudflare's R2 offering matures.
They are comparing the price using Cloudflare, which although cheap, has poor performance.
I don't know anything about these services or their pricing. Maybe AWS costs about the same as Cloudflare, but it's cheeky to have inconsistent comparisons like this. Ideally, this post/advert would provide the equivalent AWS price also (or provide Cloudflare performance numbers).
Author here. AWS is quite a bit more expensive than cloudflare, mostly because of egress charges from Cloudfront.
Cloudflare R2 latency is tricky to predict and can be anywhere from a few hundred milliseconds to 1s+ in my experience. This is for cache misses, only, of course; cache hits are comparable to AWS. Cloudflare really has every incentive to improve their product so I expect this to be much more competitive in the near future.
I haven’t really seen many R2 performance benchmarks, but 1s+ for retrieval is nuts. Is that time to first byte or total time? On what average object size?
They are comparing the price using Cloudflare, which although cheap, has poor performance.
I don't know anything about these services or their pricing. Maybe AWS costs about the same as Cloudflare, but it's cheeky to have inconsistent comparisons like this. Ideally, this post/advert would provide the equivalent AWS price also (or provide Cloudflare performance numbers).