Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a Python application that I'm serving via IIS using ISAPI-WSGI. I've got it in its own application pool so that I can restart the Python interpreter whenever I want without disturbing other applications. I don't expect any more than 2 or 3 people to access it at any given time. Is there any reason for me to change the max number of worker processes to greater than the default of 1?

Also, what criteria should I consider when deciding how many worker processes to allocate? Is it just about concurrency or are there other factors?

share|improve this question
up vote 3 down vote accepted

One worker process is enough in my opinion. Consider that requests are queued, not rejected, when another request is being served and no more threads are available in the process (I'm assuming that the process is multi-threaded).

share|improve this answer
Agreed. 2-3 people doesn't warrant any more workers. – squillman Jun 3 '09 at 14:44

It depends on your application hit. By defaults one Worker process for a application pool. If you increase the count of worker process more than one then it is called as Web Garden , for this You need to take care if there is in-proc session management.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.