Putting lighttpd fcgi into a traffic context

Alistapart.com did about 5 million hits in two and half days and it did that on the default *4* dispatch.fcgi processes.

Four.

4.

·:· Posted 27 August 2005, 00:09 by Jason Hoffman to Lighttpd  |  

  1. Impressive.

    I assume that was on a dedicated server in the new server farm?

    — topfunky    27 August 2005, 00:59    #
  2. To add the conclusion which the normal people can draw from that: you don’t need four.

    One would be silly, because you’ll run out of dispatches with any kind of concurrency level, but two will be sufficient.

    — Marten Veldthuis    27 August 2005, 02:22    #
  3. Yeah, whatever. But does it scale ? :p

    — Luc Heinrich    27 August 2005, 07:03    #
  4. Apparently it does ;)

    — Jacques Marneweck    27 August 2005, 22:23    #
  5. Yeah, but, is it mature ?

    =)

    — Shanti Braford    29 August 2005, 00:17    #
  6. Since the site’s content is mostly static, I can safely assume that rails just cached the content, and lighttpd served 99% of the requests

    — lorewarden    29 August 2005, 07:31    #
  7. Actually – and a forthcoming ALA article will detail this, there isn’t any static content, it’s all delivered live, with a minimal (due to time constraints) amount of caching going on.

    — Dan Benjamin    30 August 2005, 16:07    #
  8. Ok – my observation was based on the fact that responses don’t contain a session id… perhaps you have disabled sessions?

    — lorewarden    31 August 2005, 08:36    #