performance

Results of running Lighttpd as a static file server for Drupal 6

Google webmaster tools - Time spent downloading a page (in milliseconds)

In my blog post Running Lighttpd as a static file server for Drupal 6 on a Debian GNU/Linux server I describe how I set up a static file server here on xdeb.org. I mentioned there that I have not done any benchmarking on the improvements. I still haven’t, but I found some interesting information on Google webmaster tools.

I use Google webmaster tools to submit my sitemaps. One or two times a year I go there to see if everything is in order. They have done some updates since I was there last and this time I found “Crawl stats” under “Diagnostics” (they may very well have been there for a long time but i found them now).

The image show the chart for “Time spent downloading a page (in milliseconds)”. Notice the big drop in late July. That’s when I implemented Lighttpd as static file server.

The average time Google spent on downloading a page went from well over 1000 ms to around 600 ms. I’m very pleased with that result.

Running Lighttpd as a static file server for Drupal 6 on a Debian GNU/Linux server

Lighttpd web serverI found Robert Douglass article Using Lighttpd as a static file server for Drupal and thought it would be interesting to try out. Check also out the Lighttpd home page (pron. lighty).

There are two main reasons for using a separate server for static files. The first is to offload the main server, e.g. Apache with mod_php, letting it only handle the dynamic requests. The second is to allow browsers to download files in parallel and without the overhead of cookies etc.

After I implemented the static file server Yslow gives xdeb.org Grade A with a score of 94.

Syndicate content