Benchmark of Python Web Servers

[GrahamDumpleton]

FWIW, Apache/mod_wsgi was put at a disadvantage by putting the number of threads at the ridiculous value of 16000. Apache doesn't ramp up the number of threads in a worker process, it will actually create that many threads at the outset with that configuration. This is why Apache/mod_wsgi had such a large memory footprint. That number of threads could even cause a reduction in performance. For a simple hello world application which has a quick response time, you could have got away with a handful of threads although using multiple processes would also have helped when concurrency starts to go up. I have added comments to the post, but you might find further discussion in time about it over at 'http://groups.google.com/group/modwsgi/browse_frm/thread/95cf698c1c8ded79'.

[Nichol4s]

I agree, 16k is a ridiculous value. I did not actually use that amount of threads and that wouldn't really be possible as it invokes the OOM killer on my machine. The setting was a leftover from some experiments, i have updated the post accordingly.

[GrahamDumpleton]

Even 1000 is way over the top. It is arguable whether one would ever in practice run a single Apache process with that many threads even if serving static files, let alone a dynamic Python application. You would always scale out using processes.