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

Interesting for me to see DigitalOcean perform so badly (in this particular metric), especially since they seem to be pretty fast for me in general.



My 2c:

DNS latency is only one factor in overall perceived performance, and it can be affected greatly by routing, traffic load, and other factors. Additionally, many requests you'll make will likely go through a resolver with caching anyhow, so that too can have a significant impact on perceived latency.

Thus DO (or any provider for that matter) only really needs to provide reasonable resolution times from their servers to be effective.

A more important matter is consistency, i.e. are they consistently returning responses or are they actually dropping packets due to load. With a service that's growing quickly, keeping up with the increase in load on their network probably presents a more significant problem.


They recently switched to using CloudFlare, look at the detail graphs - http://www.dnsperf.com/provider/DigitalOcean

I'm not sure why they're still so high though.




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

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

Search: