Hacker News new | past | comments | ask | show | jobs | submit login

The article exaggerates the most likely effects of this, which are a mild improvement in latency and very little in throughput. If you're in a country with very poor international connectivity, it might be possible that your 20 Mbit connection is downloading at Kbit speeds due to choosing the wrong CDN site, but that won't be the case for most people. The common case is that throughput is not really affected--- typical downloads from well-provisioned sites on the wrong side of the Atlantic max out my DSL anyway. When they don't, it's almost always a problem with the particular mirror's last-mile connectivity, not with the transatlantic cable.



I think you misunderstand how this works. Poor geo-targeting results in increased latency which is directly correlated with throughput and it increases congestion.

Fixing that has tremendous benefits.


I've never seen a significant difference in throughput on a home connection due to a US/EU mistargeting, at least, certainly not on the level of Mbits being reduced to Kbits. I just tested now, and downloading from a California mirror is able to max out my DSL quite easily (I'm in Denmark). I do get lower latency from European mirrors, but not higher throughput, because both can saturate the link.


Everyone who has this problem will be glad to hear you were not able to reproduce it.


Are you using the Google or OpenDNS DNS Servers?

That's the real issue - previously these DNS servers did not work well with CDNs because they didn't send the location of the client making the request to the origin server. This extension fixes that problem.

If you aren't using these DNS servers then CDNs probably route your requests properly.


I am using Google's, but that isn't really the point; the point is that in real-world usage, the example in the article of a multi-Mbit connection ending up with Kbit-level throughput due to being routed to the wrong CDN is very unlikely if you live in the U.S. or Europe. It would require either a really broken TCP stack, or gigantic satellite-internet-level latencies for latency to constrain throughput that much.


Yes, you are probably right about the throughput. The latency problems are very valid though, and make websites seem remarkably slower.

I live in Australia at the end of a very long trans-pac pipe, and properly configured CDNs make a huge difference. A great example is how a few cheap ISPs here route based on price, not latency. That meant that when Amazon opened their Singapore dataceter a visitor from Australia (using one of these ISPs) could be routed via the US West Coast.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: