3 ms·
200ms is enough for an RTT from Boston-Auckland-Boston. S3 is slow. You’re single digit milliseconds from us-east-1 under optimal conditions.
by trillic 3y ago
200ms is enough for an RTT from Boston-Auckland-Boston. S3 is slow. You’re single digit milliseconds from us-east-1 under optimal conditions.
- Terretta 3y agoYep, using a ping history: Boston - DC shows about 13ms: https://wondernetwork.com/pings/Washington/Boston https://wondernetwork.com/pings/Washington/Boston Boston - Auckland shows about 207ms: https://wondernetwork.com/pings/Washington/Auckland https://wondernetwork.com/pings/Washington/Auckland From anywhere, S3 used to (10+ yrs ago) seem slow enough for a person to feel a delay, 400ms - 800ms plus RTT ping time, but people did and are seeing results sub-200ms perception threshold, i.e., "Average latency per file was 72.3ms" -- but some requests still take a literal second: https://github.com/opendatacube/benchmark-rio-s3/blob/master/report.md https://github.com/opendatacube/benchmark-rio-s3/blob/master... Even a 15 years ago, though, people were seeing sub-100ms to S3: https://www.quora.com/What-are-typical-latencies-for-static-content-in-S3-vs-Cloudfront https://www.quora.com/What-are-typical-latencies-for-static-...