Generally speaking, you need to think of concurrency. At most, your WSGI setup will not be able to handle more concurrent requests than it has threads to handle them. This will also depend on your use of nginx as a proxy, because it buffers requests and responses to a degree, thus freeing up python threads quickly to be used for other requests.
Other considerations include how many database connections do you *really* want open at once? Ultimately, if you are just getting started, then use a sensible default (eg 1-2 process with 5-10 threads), and see how it copes. For more information, search this mailing list extensively, because this has been hashed, rehashed, and rerehashed many times here. Thanks! Jason Garber On Tue, May 4, 2010 at 10:55 AM, Boris Schaeling <[email protected]> wrote: > Are there any guidelines how to find a reasonable value for processes and > threads in daemon mode? For example how do I know if x processes and y > threads are sufficient? > > <http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading> recommends > to "plan ahead and make sure the number of processes and threads defined is > adequate to cope with the expected load". Now a simple to interpret number > like "mod_wsgi load average" would be great. :) As it doesn't exist are > there any mod_wsgi-specific guidelines out there to calculate such a number > yourself? > > Boris > > -- > 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]<modwsgi%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/modwsgi?hl=en. > > -- 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.
