w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 21.08.2007 18:15:40 von scott
w3wp.exe *32 process ...... seem to have 1 per user on webserver 1 and on
webserver 2 i seem to have a single process that all users use !!!
anyone know why ?
iis6
asp.net 2
server 2 is dual core, dual cpus
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 21.08.2007 18:44:03 von Kristofer Gafvert
Hello,
What do you actually mean by "user"? Do you mean that for each request
coming to IIS, a new w3wp.exe process is launched? Or do you mean
"customer" as in shared hosting?
Each application pool has its own w3wp.exe process, so maybe you have one
(1) application pool on one server and multiple application pools on
another?
--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info
Scott wrote:
>w3wp.exe *32 process ...... seem to have 1 per user on webserver 1 and on
>webserver 2 i seem to have a single process that all users use !!!
>
>anyone know why ?
>
>iis6
>asp.net 2
>server 2 is dual core, dual cpus
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 22.08.2007 10:35:23 von scott
> What do you actually mean by "user"? Do you mean that for each request
> coming to IIS, a new w3wp.exe process is launched? Or do you mean
> "customer" as in shared hosting?
sorry, should have explained better. Every users conncetion to IIS6 index
page on route or asp.net 2 app spawns a new w3wp.exe process.
On my new webserver this is not the case , all new users connection share
single w3wp.exe process.
> Each application pool has its own w3wp.exe process, so maybe you have one
> (1) application pool on one server and multiple application pools on
> another?
Interesting.
basically i used host headers, IIS contain 5 domains, all domains point to
same wwwroot dir, all domain uses the default app pool.
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 22.08.2007 10:39:36 von David Wang
On Aug 22, 1:35 am, "Scott" wrote:
> > What do you actually mean by "user"? Do you mean that for each request
> > coming to IIS, a new w3wp.exe process is launched? Or do you mean
> > "customer" as in shared hosting?
>
> sorry, should have explained better. Every users conncetion to IIS6 index
> page on route or asp.net 2 app spawns a new w3wp.exe process.
>
> On my new webserver this is not the case , all new users connection share
> single w3wp.exe process.
>
> > Each application pool has its own w3wp.exe process, so maybe you have one
> > (1) application pool on one server and multiple application pools on
> > another?
>
> Interesting.
>
> basically i used host headers, IIS contain 5 domains, all domains point to
> same wwwroot dir, all domain uses the default app pool.
There is no way to have every user connection handled by a different
and new w3wp.exe. Not to mention that would be horrible for
performance. What exactly are you trying to accomplish?
Your current configuration assures that all requests to any of the 5
domains are handled by the w3wp.exe of the same Application Pool.
Thus, what you observe is exactly what you configured. If you want a
different result, then please CLEARLY explain what you actually want
to do.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 22.08.2007 11:06:39 von scott
> There is no way to have every user connection handled by a different
> and new w3wp.exe. Not to mention that would be horrible for
> performance. What exactly are you trying to accomplish?
>
> Your current configuration assures that all requests to any of the 5
> domains are handled by the w3wp.exe of the same Application Pool.
> Thus, what you observe is exactly what you configured. If you want a
> different result, then please CLEARLY explain what you actually want
> to do.
Thanks for the reply ... again sorry for not explaining clearly enough.
Essentially i have achived when i was trying to achieve .. i.e im not
spawning processes anymore on new server.
I was simply looking for an explanation regading why w3wp.exe process were
getting spawned on the old webserver.
I can clearly state that every time i opened a browser , connected to my
sites index page, at this stage a new w3wp.exe process would spawn. If i
opened a new browser and do the same again a see another w3wp.exe process on
the server - honest ! this is what is happening. I was simply looking to
understand why this would be the case so i can prevent it happening again ..
thats all.
Thanks again for your time
Scott
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 22.08.2007 11:11:38 von David Wang
On Aug 22, 2:06 am, "Scott" wrote:
> > There is no way to have every user connection handled by a different
> > and new w3wp.exe. Not to mention that would be horrible for
> > performance. What exactly are you trying to accomplish?
>
> > Your current configuration assures that all requests to any of the 5
> > domains are handled by the w3wp.exe of the same Application Pool.
> > Thus, what you observe is exactly what you configured. If you want a
> > different result, then please CLEARLY explain what you actually want
> > to do.
>
> Thanks for the reply ... again sorry for not explaining clearly enough.
> Essentially i have achived when i was trying to achieve .. i.e im not
> spawning processes anymore on new server.
>
> I was simply looking for an explanation regading why w3wp.exe process were
> getting spawned on the old webserver.
>
> I can clearly state that every time i opened a browser , connected to my
> sites index page, at this stage a new w3wp.exe process would spawn. If i
> opened a new browser and do the same again a see another w3wp.exe process on
> the server - honest ! this is what is happening. I was simply looking to
> understand why this would be the case so i can prevent it happening again ..
> thats all.
>
> Thanks again for your time
> Scott
What you describe could happen if:
1. You have a Web Garden >1. You will notice the number of w3wp.exe
top out at the size of the Web Garden, determined by different
connections
2. Recycle by Request=1 for the Application Pool. Every request would
cause w3wp.exe to recycle, bringing up a second w3wp.exe while the
original one exists temporarily -- Depending on request load and
whether overlapped recycling is allowed, this can be either 1 to N
w3wp.exe momentarily around where N depends on the server's processing
capabilities
3. You have orphaning enabled, and each of your requests are causing
the w3wp.exe to be orphaned by crashing/hanging it. This will have no
upper boundary on number of orphaned w3wp.exe
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
Re: w3wp.exe - 1 per user on 1 server , 1 for all users in another server ?
am 26.08.2007 18:07:47 von scott
thanks for reply.