4 ms·
I noticed very strange but consistent performance behavior from Google Public DNS. Even though a DNS record was cached, the response time was in the range of 20
by nodesocket 13y ago
I noticed very strange but consistent performance behavior from Google Public DNS. Even though a DNS record was cached, the response time was in the range of 20-30ms, which is absolutely horrible. When I switched over to OpenDNS, cached response times dived down to 1ms. Needless to say just made the switch on all the servers to OpenDNS. Can anybody explain this behavior?
Here is the GitHub gist showing the output:
https://gist.github.com/nodesocket/786e3b879f74c7787ca6 https://gist.github.com/nodesocket/786e3b879f74c7787ca6
- remosi 13y agoWhere in the world are you? Do you have a traceroute to 8.8.8.8?
- nodesocket 13y agoI am in DigitalOcean (San Francisco). The answer is simply distance/routing. I am guessing OpenDNS has an anycast node in DigialOcean (SF), where Google Public DNS does not. A ping tells the story. ping 8.8.8.8 => 24ms ping 208.67.222.222 => 1ms
- mburns 13y agoA traceroute would tell the story better.
- dsl 13y agoFrom DigitalOcean in SF I'm hitting the OpenDNS Palo Alto datacenter. Google is going to San Jose. Remember OpenDNS is a real business working to provide a service to real paying customers, Google DNS is just a fun little project of building an OpenDNS clone.
- adamseabrook 13y agoI believe all the DO droplets default to 8.8.8.8 so Google are probably applying some rate limiting across the DO network block during usage peaks.