Last post Jun 16, 2008 08:30 AM by email@example.com
Jun 15, 2008 09:26 AMfirstname.lastname@example.org|LINK
I am using IIS 6.0 and have 4 worker processes running. How can I identify which worker process is running for which asp.net application?
Jun 15, 2008 10:19 AM|OWScott|LINK
iisapp from the command prompt.
Jun 15, 2008 10:21 AMemail@example.com|LINK
Found the answer - I used IISApp.vbs to map the worker process to its application pool as described here:
I had had to Application Pools but one was set to a web garden with 3 worker processes hence 4 worker processes in the task manager.
Jun 15, 2008 10:29 AMfirstname.lastname@example.org|LINK
Thanks Scott that was the solution I found too. There were 3 web applications under 1 Application Pool and the
Maximum number of worker processes box had been set to 3 under the
performance tab within the Web Garden section. I don't remember setting this so would it automatically increase when I added applications to the same application pool?
Jun 15, 2008 05:41 PM|OWScott|LINK
Funny, the article on ASP Alliance is mine too, I forgot that it was posted there.
No, the Web Garden setting doesn't change automatically. That is normally 1 and for 95% of the cases, it's better at 1, no matter how many sites are in the app pool. That allows multiple app pools to serve the sites (it won't balance sites across the 3
app pools, it will just have 3 app pools each handling all 3 sites). If you're using InProc session state for ASP.NET pages, you'll run into issues with the Web Garden settings, but if you don't depend on session state, or if use out-of-process session state,
then a web garden works if there is a particular reason for it.
Jun 16, 2008 03:04 AMemail@example.com|LINK
Ok thanks Scott. The problems I ran into that led me to discover that 3 worker processes were running was some odd caching behaviour, I then found out that:
“Because Web gardens enable the use of multiple processes, each process will have its own copy of application state, in-process session state, caches, and static data. Web gardens should not be used for all applications, especially if they need to maintain
state. Be sure to benchmark the performance of the application before deciding whether Web garden mode is appropriate"
I will set the app pool back to 1 worker process for the time being until we learn a bit more about it.
That is normally 1 and for 95% of the cases, it's better at 1, no matter how many sites are in the app pool. That allows multiple app pools to serve the sites (it won't balance sites across the 3 app pools, it will just have 3 app pools each handling all 3
Jun 16, 2008 08:30 AMfirstname.lastname@example.org|LINK
Be sure to check www.iis.net for help with IIS.