ASP.NET Thread Usage on IIS 7.0 and 6.0

Links of the Week September 19 2007

Chris Love's Official Blog - Professional ASP.NET — Wed, 19 Sep 2007 16:53:04 GMT

Everyone seems to be coming off vacation and my book is done so now to list the resources to make us

WCF Request Throttling and Server Scalability

Wenlong Dong's Blog — Mon, 21 Apr 2008 10:11:02 GMT

Two Threads per Request In .NET 3.0 and 3.5, there is a special behavior that you would observe for IIS-hosted

Hidden Gems - Not the same old 3.5 SP1 post

Readed By Wrocław NUG members — Thu, 14 Aug 2008 03:56:33 GMT

Folks were hassling me in the comments for not posting the picosecond that .NET 3.5 SP1 came out (or

WCF Request Throttling and Server Scalability

The .NET Endpoint — Thu, 14 Aug 2008 07:24:34 GMT

(Copied from http://blogs.msdn.com/wenlong/archive/2008/04/21/wcf-request-throttling-and-server-scalability.aspx

WCF Request Throttling and Server Scalability

The .NET Endpoint — Thu, 14 Aug 2008 07:39:31 GMT

(Copied from http://blogs.msdn.com/wenlong/archive/2008/04/21/wcf-request-throttling-and-server-scalability.aspx

Hidden Gems - Not the same old 3.5 SP1 post

ASPInsiders — Thu, 14 Aug 2008 07:59:06 GMT

Folks were hassling me in the comments for not posting the picosecond that .NET 3.5 SP1 came out (or,

re: ASP.NET Thread Usage on IIS 7.0 and 6.0

sjuranek — Sat, 25 Oct 2008 23:26:55 GMT

This was a great write up that I found very helpful for the application I'm working on. My application was only handling 24 simultaneous requests until I made the registry change. However one thing that hung me up a while is that the registry key must be: maxConcurrentRequestsPerCPU with CPU in all caps. You have 'Cpu' several times above and Process Monitor helped me find that w3wp wasn't finding it.

Also, I tried using the aspnet.config technique since I have .NET 3.5 SP1 loaded but it doesn't seem to work.

re: ASP.NET Thread Usage on IIS 7.0 and 6.0

tmarq — Mon, 27 Oct 2008 19:52:26 GMT

Registry key names are not case sensitive, so maxconcurrentrequestspercpu will work as well as MaxConcurrentRequestsPerCPU. In 3.5 SP1, you can use aspnet.config, as shown in the post. Be sure aspnet.config is located in the same directory as the framework:

x86: %windir%\Microsoft.NET\Framework\v2.0.50727\aspnet.config

x64: %windir%\Microsoft.NET\Framework64\v2.0.50727\aspnet.config

Also note that <system.web> must be contained in the <configuration> section.

IIS 7.0, DebugDiag, WinDBG & .Net Framework

Yong Hee Park's Blog — Thu, 11 Dec 2008 09:17:12 GMT

최근 진행된 SCOM/SSRS 관련 Troubleshooting에서 처음으로 64bit Windows 2008에서 작동 중인 IIS 프로세스 디버깅을 시도해었습니다. 물론 Managed

re: ASP.NET Thread Usage on IIS 7.0 and 6.0

RiSingh — Thu, 22 Jan 2009 00:53:01 GMT

maxConcurrentRequestsPerCPU setting in registry has to be spelled correclty.

I wasted a lot of time in setting it to maxConcurrentRequestsPerCpu and it didn't work. Once I changed the dword to maxConcurrentRequestsPerCPU , all my 50 concurrent requests started coming in, instead of just 12 earlier.

I would suggest the author to write a official KB article on this.

ASP.net Hang in IIS 7.0

Useful IIS/ASP.NET Information provided by Microsoft Support Teams — Fri, 13 Feb 2009 22:43:39 GMT

When hosting an ASP.net web application on IIS7, and you have the application running in integrated pipeline

ASP.net hang in IIS 7.0

IIS troubleshooting, administration, and concepts. — Fri, 13 Feb 2009 22:46:02 GMT

When hosting an ASP.net web application on IIS7, and you have the application running in integrated pipeline

ASP.net Hang in IIS 7.0

Microsoft Support Team's IIS Blog — Fri, 27 Mar 2009 01:41:29 GMT

When hosting an ASP.net web application on IIS7, and you have the application running in integrated pipeline

re: ASP.NET Thread Usage on IIS 7.0 and 6.0

stombrown — Wed, 08 Apr 2009 07:43:18 GMT

any behavior changes in WS08?... was wondering about the "this change has not been ported to WS08" comment.

re: ASP.NET Thread Usage on IIS 7.0 and 6.0

tmarq — Wed, 08 Apr 2009 23:56:38 GMT

In reference to IIS allowing different aspnet.config files to be specified for each Application Pool, I found out today that it was not ported to WS08. The change was only made to Windows 7.