What triggers IIS to spawn new worker process? RRS feed

  • Question

  • User-2031132340 posted

    I was testing my web api using Apache Jmeter and notices that when I send simultaneous requests that are equal or greater than the number of allowed worker processes, then IIS will automatically spawn a new process.  For example if I set the number of processes to 2, it starts with one, but if I sent 2 or more requests, it spawns another processes.  Similarly if I have allowed 8 worker processes, I can send less than 8 requests but it will use only one process, anything above 8 will add a new process until the number of requests doubles, 16 will add yes another worker process.  

    How does IIS decide when it is time to spawn a new process?  

    Tuesday, December 17, 2019 5:32 PM

All replies

  • User-474980206 posted

    Microsoft does not give out this information (as it can change with different versions and service packs), only the suggestion that you not use web gardens unless you really need them, as it decreases performance and reliability.

    unless your site has long running processes locking up threads, you should not enable this feature.  you would better off fixing the site to not behave badly.

    note: if you want a real performance boost, convert to asp.net core.

    Tuesday, December 17, 2019 9:44 PM