FYI.

http://basicverbs.com/benchmark-of-django-deployment-techniques/

Interesting how using nginx front end to Apache makes such a difference.

One doesn't know the full configuration they are using, but one could
speculate that the high response time and reduced throughput for
Apache for 250 clients could be due to clash between keep alive
connections and insufficient Apache server child processes/threads. In
other words, need for Apache to handle keep alive connections and as a
consequence not releasing client connections immediately, could tie up
threads and so if not sufficient number of Apache server processes,
could be maxing out on thread usage and not able therefore to handle
increased load. Sticking nginx in front of Apache would certainly
assist with that as keep alive is then handled by nginx using an event
driven model and so can handle more concurrent connections. Because
nginx only uses HTTP/1.0 for proxy connections, the connections
between nginx and Apache would always be released immediately
regardless of whether keep alive turned off or not in Apache. As such,
Apache can get back to handling requests straight away, thus allowing
it to do more with less threads.

The other possibility may simply be that for that number of concurrent
connections, five single threads daemon mode processes isn't enough.
Nothing is said about number of processes/threads used for other
hosting mechanisms and since some fastcgi solutions dynamically create
processes, possibly as many as 100, they may have more headroom to
handle more connections where fixed number of processes/threads in
mod_wsgi daemon mode is limiting what can be achieved.

Overall what these results do show is that there isn't a great deal of
difference between various hosting mechanisms and as such it comes
back to it being more important that you tune your application and
database rather than participate in a pissing contest over which
solution may be quicker.

Graham
-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.


Reply via email to