Comment by treis
3 years ago
This is one of those problems that basically no one has. RTT from Japan to Washington D.C. is 160ms. There's very few applications where that amount of additional latency matters.
3 years ago
This is one of those problems that basically no one has. RTT from Japan to Washington D.C. is 160ms. There's very few applications where that amount of additional latency matters.
It adds up surprisingly quickly when you have to do a TLS handshake, download many resources on pageload etc. The TLS handshake alone costs 3 round-trips over the network.
TLS is cached though. Your 3 round trips is 1/2 second on initial load but then should be reused for subsequent requests.
Resources should be served through a CDN so you'll get local servers for those.