On 28 November 2010 02:53, JE <[email protected]> wrote: > Hi! > > I thought a little bit about your answer. > > On Nov 26, 5:45 am, Graham Dumpleton <[email protected]> > wrote: >> >> Thus up to 100 internal connection requests can queue up. > [...] >> >> If that limit is exceeded, then it will at that point fail and a retry >> mechanism within mod_wsgi will kick in: > > Let's say I configure mod_wsgi daemon mode to accept at the most 1 > connection at a time (processes = 1, threads=1). > That means that in a high traffic scenario - that I actually need to > configure > Apache's max_clients to 1+100+X > where X is number of clients that request static resources. > Do I also need to factor the connections in that are retrying to > connect to mod_wsgi? These are trying for about 30 seconds to connect, > right ? > I'm not sure how I should do it. > My goal is to configure mod_wsgi in such a way, that it should not eat > up all available connections defined by max_clients, eventhough it > cannot process them. > This would stop Apache from handling requests for static resources.
If you are that paranoid about static resources not being able to be handled, put a nginx server in front of Apache for handling static media and have nginx proxy only dynamic web application requests through to Apache/mod_wsgi. In other words, don't try and make one tool do everything as static file handling and dynamic web applications generally have different requirements. Apache is not the best at static file serving and you are much better off using nginx for that. 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.
