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. Thank you in advance ! Best regards, Jan-Eric -- 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.
