views:

171

answers:

1

I'm running IIS 7 on Server 2008, with a single AppPool for an application which is basically just a collection of ASP.NET WebMethods. Some of these methods process for hours before they return.

What's weird, is that sometimes when I launch multiple simultaneous requests IIS spins up a single w3wp process (and seems to share it amongst the requests) and other times it spins up multiple w3wp processes (1 for each request).

I am always careful to use task mgr and view processes for all users when observing this. Can anyone explain this inconsistent behavior?

+1  A: 

By default each app pool gets 1 w3wp process, but in a web garden multiple w3wp processes can exist per app pool.

Edit: A little more info about web gardens

Matt Dearing
Do you know how the web garden decides whether to kick off a new w3wp process for a request, or whether to share a single w3wp process for multiple requests?
manu08
I am not sure when another process kicks off, but you can control the maximum number of processes in iis. In IIS6 Just find the app pool right click, properties, and you will see maximum worker processes (in ii7 it is under advanced settings of the app pool).
Matt Dearing