What makes my website slow? DNS

This blog post is 8 years old! Most likely, its content is outdated. Especially if it's technical.

Pagetest web page performance test is a great tool for doing what Firebug does but not in your browser. Pagetest can do repeated tests to iron out any outliers. An alternative is Pingdom tools which has some nifty sorting functions but is generally the same thing.

So I ran the homepage of my website on it and concluded that: Wow! Half the time is spent on DNS lookup!

The server it sits on is located here in London, UK and the Pagetest test was made from a server also here in the UK. Needless to say, I was disappointed. Is there anything I can do about that? I've spent so much time configuring Squid, Varnish and Nginx and yet the biggest chunk is DNS lookup.

In a pseudo-optimistic fashion I'm hoping it's because I've made the site so fast that this is what's left when you've done all you can do. I'm hoping to learn some more about this "dilemma" without having to read any lengthy manuals. Pointers welcomed.

Lucian

23 October 2009

Well, it's pretty fast already. It loads in 0.5-2sec on my machine. I think any further effort spent on optimisation will have very little impact of the user experience.

Fernando Rodriguez

23 October 2009

I wish mine was half as fast...

It would be very interesting to know how you got this far in optimizing it.

Claes Ström

23 October 2009

Could it be that you have your NS service from MyDomain who has many many customers on their servers.
This delay should only happen when your nearest DNS don't have the domain cached.
You have 900 seconds TTL on www.peterbe.com, which means that local DNS servers needs to ask mydomain again quite often...

BTW I tried it on one of my static sites and got a lot of bogus results. But the DNS resolving time for my .se address hosted on my own TinyDNS was a third of yours with the same UK testserver as you used (I think). Maybe is .SE faster than .COM also.

BTW2 We meet @ Euro DjangoCon where we had a short lunch together one day at the conferance.

Graham Higgins

23 October 2009

A useful URL, thanks Peter. I was able to make some highly effective tweaks. I'm in the UK too and so is my server. My DNS is served by Zoneedit.com and it's resolving for me in 0.15s.

Mustapha Benali

23 October 2009

Hi Peter,

Do you have nscd (Name Service Cache Daemon) installed on the machine? I guess it will help

Claes Strröm

23 October 2009

It's the "clients" DNS server who could make use of a DNS Cache, not Peters....

Patrick Meenan

23 October 2009

FWIW, caching is disabled on the test systems on purpose but it will leverage any caching done by the ISP or further upstream (which is where the TTL becomes important).

Patrick Meenan

23 October 2009

One thing to be careful with is that the UK location for WebPagetest is running with minimal to no latency (direct connected to high bandwidth data center connectivity). Odds are that for real users on DSL or other connectivity (where 50ms last-mile latency is not unusual) the bottlenecks may move and using an image sprite for a bunch of those images will help.

We're working on making the connectivity in the UK location more like what we have in the US and NZ locations where the connectivity is more in line with a consumer experience.

tcg

24 October 2009

Not sure if this kind of thing is what you're looking for, but Jeff Atwood posted somewhat recently about their change of DNS Provider for StackOverflow (here: http://blog.stackoverflow.com/2009/09/new-dns-provider/) because of DNS instability and response times. Might be a good jump-off point for great reading about speeding up your DNS.

Rodrigo Landerdahl

25 October 2009

Dude, I'm in south america and your site feels blazing fast (actually much faster than many local sites). So, no worries.

Carl Meyer

26 October 2009

Thanks for the pointer to webpagetest.com, that's a good resource!

Ivana Lukic

18 December 2012

Webpagetest is a great and very comprehensive tool that has a great options. Pingdom is its alternative, but there are also two more tools that are checking the performances of the website and both uses gps and yslow:
http://gtmetrix.com
http://tutor.rs

Bheesham Persaud

08 April 2013

The first two images now give a 404. The third one works just fine for me though.

Peter Bengtsson

08 April 2013

Sorry about that. About a year ago I rewrote my whole blog from scratch and migrated all the data from an object database into PostgreSQL and some content was not part of the database nor cached so I couldn't pick it up.

Previous:: What I hate about PIL and Image in Python 19 October 2009
Next:: iPhone push notifications for Twitter with Prowl 25 October 2009

Related:: How to deploy a create-react-app 04 November 2016; How I stopped worrying about IO blocking Tornado 18 September 2012; Is Nginx obsolete now that we have Amazon CloudFront? 28 July 2012; How much faster is Nginx+gunicorn than Apache+mod_wsgi? 22 March 2012; How I profile my Nginx + proxy pass server 16 February 2011; DoneCal homepage now able to do 10,000 requests/second 13 February 2011; ssl_session_cache in Nginx and the ab benchmark 31 December 2010; DoneCal gets a grade A (92) 27 November 2010; Javascript tip: nifty use of the console.log function in Firebug 07 November 2010; Why I gave up on JQuery UI's autocomplete 20 October 2010

What makes my website slow? DNS

http://www.webpagetest.org/test

Comments

Related posts