Last post Apr 12, 2012 03:45 PM by atconway
Apr 11, 2012 01:28 PM|amo_amas_amatit_again|LINK
Given each user logged into my website is already running in their Session / own thread courtesy of IIS, I was wondering whether IIS imposed any restrictions on the creation of threads / use of Background worker threads for each user. In particular,
does anyone know whether all users share the same pool of Background Worker threads - my guess is that they would. This would imply that for a heavily used site, the thread pool might quickly get exhausted if the website had algorithms relying on multiple
Any observations / suggestions on best practice in this area would be appreciated. (Note I am not after input on threading in general. I am only after any specifics which pertain to Threading on a web site (not a web project) running under IIS).
Apr 12, 2012 03:45 PM|atconway|LINK
I know there are thread setting that can be set at the application level (i.e. web.config - minFreeThreads, minFreeLocalRequestFreeThreads) and at the machine level (i.e. machine.config or registry) when it comes to managing thread allocation and handling
for IIS. Have a look at the following documentation to get a better understanding, and may I also suggest the
IIS Forums as well for questions like this.
ASP.NET Thread Usage on IIS 7.5, IIS 7.0, and IIS 6.0:
Optimizing IIS Performance: