worker processes?

I'm using this 2003 Server to serve up about 30 static HTML sites and about
14 ASP database-driven sites.
It's a 2-cpu box with 2 gig of RAM.
I'm playing with application pools.
Out of the 14 ASP database-driven sites, I have 10 that are nearly identical
to each other.
I'd like to put these 10 into the same application pool.
So I created a new application pool and I'm looking at the settings.
If I figure I'll have 10 sites running in this particular pool, should I set
"Maximum number of worker processes" to 10?
How exactly do worker processes correspond to a database-driven ASP site?
Thanks!

--
Scotter

Hi Scotter,

Increasing worker process number more than 1 means enable the Web
Garden feature in IIS6. It can improve reliability and performance in
some cases but will cause something like in-process session lost. So
if you ASP sites need to use session state, you shouldn't increase
the process number. The following page talks about Web Garden's
benefit and impact:

Configuring Web Gardens
http://www.microsoft.com/resources/documentation/IIS/6/all/techref/en-
us/IISRG_WAS_31.mspx

When Web Garden feature hasn't been enabled(process number = 1),
every application pool corresponds to 1 w3wp.exe worker process,
which means if you separate the 14 ASP sites into 14 AppPools and all
of them are running currently, you will see 14 w3wp.exe instances in
task manager.

Best regards,

WenJun Zhang
Microsoft Online Support
This posting is provided "AS IS" with no warranties, and confers no
rights.
Get Secure! - www.microsoft.com/security