One of the reasons for putting nginx in front of Apache/mod_wsgi is that static file handling can be offloaded to nginx, with it being much better at handling static files.
The other benefit I have described is that it isolates Apache from slow clients and removes the need to Apache to handle keep alive and so avoid it wasting processes/threads on clients that may or may not make a subsequent request. Anyway, came across a nice article that details a lot of this. http://markmaunder.com/2009/how-to-handle-1000s-of-concurrent-users-on-a-360mb-vps/ The only thing I think it doesn't mention is the specific details around how the buffering in nginx of the request headers and content up to default of 1MB serves to ensure that Apache isn't bother with requests in most cases until the request is actually all read from the client. 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.
