Earlier quoted context omitted.
This page is such a well executed interactive map. Really enjoyed it Is the math-planation of your random fact basically ( thanks to https://news.ycombinator.com/user?id=Hikikomori for correcting the lightspeed in fibre medium from 3e5 to 2e5 ! ) - lightspeed is 2e5 km/s ~ 2e2 km/ms, so/ - length (km) / 200 (km)/ms ~ K length (km) / 200 (km)/ms, so - latency (ms) ~ K' length (km) Where K is approximately 1.3 (K' is 1…
It is possible I was measuring latency in a single direction, rather than round-trip-time. My memory is a little hazy now.
AWS data center latencies, visualized
101–110 of 223 posts
Re: AWS data center latencies, visualized
#102Re: AWS data center latencies, visualized
#103Re: AWS data center latencies, visualized
#104Interesting. If you click on one of the blue circles representing a data center, it shows latencies to the other data centers. This took me a second to figure out — maybe consider adding a note along the lines of “click to select a data center” on the site?
Author here. This is great feedback, thanks.
Perhaps if you selected a datacenter, and it switched to a 2-d projection with that datacenter at the center of the map, it would be better?
Or perhaps augment the visualization with a table?
Re: AWS data center latencies, visualized
#105There're three certainties in life death, tax and network latencies.
Re: AWS data center latencies, visualized
#106Obviously the biggest contribution to latency is distance. But there's also some close-ish regions with poor latency because there's not fiber running directly between them (for example, over the poles) Are there an examples of regions which dramatically violate the triangle equality? (That is, where the A--C latency is much worse than the best A--B + B--C latencies)? Just as a curiosity, could you use that idea to "…
Now there are some issues with this methodology (all common issues with ICMP/RTT measurements + traffic was not really routed through the "relay" probe), but such pairs do exist.
[1] https://theses.hal.science/tel-03666771/document (see page 84 for an example; if you can read French :-))
Re: AWS data center latencies, visualized
#107Re: AWS data center latencies, visualized
#108Us-east-1 is hard to beat. Close to the network centrality of the of the internet, low latency to both the west coast and Europe.
> Close to the network centrality of the of the internet Most of the Internet is fractured even though technically publically routable. E.g., for someone living in China the US isn't anywhere near "network centrality". If an internet centrality exists, it is somewhere in France or the Netherlands - usually cross-continent traffic goes through there, they have dedicated interchanges for that.
You are right, the best region that optimises median latency against all internet users over the world is `us-west-3`, which is Paris - I believe. Likely because it has much better latency towards Asia where the majority of internet users are.
I also investigated which two regions to choose for a multi-region setup, which ends up being London and Japan.
Re: AWS data center latencies, visualized
#109I raise this because I've been in multiple system architecture meetings where people were complaining about latency between data centers, only to later realize that it was pretty close to what is theoretically possible in the first place.
Re: AWS data center latencies, visualized
#110Earlier quoted context omitted.
As a quick workaround, you can set a CSS filter on the whole page: Either use dev tools to put a rule `filter: hue-rotate(60deg);` on the `body` element, or simply run `javascript:void(document.body.style.filter='hue-rotate(60deg)')` from the url bar.
Nice hack, thank you! :-)