I have been looking all over the internet and still not able to find how to change default values of maxWorkerThreads for a CLR threadpool using IIS 7. When I select and application pool and go to advance settings I do see process model (which MSDN is harping about everywhere on the internet) in order to configure values for max and min worker threads. But I'm not able to find where these property names are hidden and whenever I open aspnet.config file it has no default element by the name processModel. And also when I read this article http://blogs.msdn.com/b/tmarq/archive/2007/07/21/asp-net-thread-usage-on-iis-7-0-and-6-0.aspx it says go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\2.0.50727.0 and change MaxConcurrentRequestsPerCPU value which is not present there by default but in .net 4.0 value of this property is 5000 by default. Does that mean I still need to go to above mentioned registry path and configure it's value to 5000 (may be that path is for .net 2.0 i need to go for a path giving me a way to configure the same property in .net 4.0).Since this article is saying that .net 4.0 depends on maxConcurrentRequestPerCPU rather than maxConcurrentThreadsPerCPU.
And the biggest confusion is that if I go to IIS manager and select webserver and in the right pane (in IIS manager) click ASP I can change Threads per processor limit. How does this thread per processor limit is different from maxWorkerThreads per processor or maxConcurrentThreadsPerCPU. I read that Threads per processor limit is the nummber of threads created by IIS so I would assume that its IIS' I/O threads not CLR threadpools worker thread. Is my assumption right or wrong?
Please clear all these doubts of mine, MSDN is not giving clear cut difference between Threads per processor limit, maxConcurrentThreadsPerCPU and maxWorkerThreads of CLR. It's all so confusing.