I hate to nitpick [ no, I don't ... ;-) ]
but you will *always* be in an application pool,
regardless of whether you are in an IIS5 AppPool,
or ins an IIS6 AppPool.
The key thing is that that applies *only* to IIS 6 AppPools.
The rest of your premises are correct.
re:
Thanks
You're very much welcome... ;-)
That only applies when using IIS 6.0 application pooling.
I'm using IIS 6.0 as well.So it means that my application is always
under an application pool ,even if there are 3 workerprocesses defined
in that application pool,there shouldn't be any problem using session
states because any request would be redirecteded to the appropriate
workerprocess and session state is kept.
Thanks
That only applies when using IIS 6.0 application pooling.
In IIS 5.0 isolation mode, you can have
only as many worker processes as CPUs.
In worker process isolation mode,
multiple CPUs can service a single worker process.
oh,I forgot to ask something.
In the article you introduced,it says that if I don't close the
connection,it means that the requests are always sent back to the
right process.I think this dose solve the problem of Inproc session
state,but I have no idea how good or bad is to keep the connection
alive and not close it ,I don't know which connection it is talking
about and generally it's supposed to be closed or left open!!!???
Thanks
Exactly.
So I'd like to confirm this one as well,thanks .
Whn there is 2 worker processors on a machine which has two
processors,one request from user#1 to the application might be
handed over to workerproccess#1 and the next request from the same
user might be handed over to the Workerprocess#2. Right? I think
that's why Inproc session state is not working in this scenario.
Thanks for your help
Exactly.
So, you mean that if their application is set to use both cpus it
mean there should be 2 workerproceesses to take advantage of
having 2 processors in the web server and with such a
configuration Inproc seesion management(using session variables)
don't work. Am I right?
Thanks
You'll need to use either State Server or SQL Server state
management
if you turn on the web garden feature, since ASP.NET is no
longer
tied down to a single processor and/or a single process.
State management has nothing to do with the number of processors
a server has, except for needing out-of-process state
management,
but you do need to be careful with your configuration.
If you want all processors to share ASP.NET tasks,
you should turn the webGarden mask, in the processModel to true.
You will also need to set the cpuMask="[bit mask]"
to set the number of CPUs available for ASP.NET processes
(webGarden must be set to true if the bit mask is set)
If you want to use IIS 6.0 application pooling, make sure the
application keeps a connection open so that its requests are
sent back to the appropriate process.
See :
http://msdn.microsoft.com/library/d...l/cpconperformanceapplicationpoolsettings.asp
and see
http://msdn.microsoft.com/library/d...us/cpgenref/html/gngrfProcessmodelSection.asp
for the cpu mask settings.
I'm having a webserver with 2 processors .I read an article
somewhere that state mamangement on 2 processors in an ASP.NET
application is different with one processor.Is that right?
Thanks