B
Brian Gideon
I'm having a problem with the amount of time it takes to initialize an
application pool on IIS 6.0. Upon the first request to an ASP.NET
page the worker process (w3wp.exe) starts up. The problem in my case
is that it takes more than 5 minutes to begin servicing requests after
the initial startup. During that agonizingly long period the process
is doing nothing...and I mean absolutely nothing...0% CPU and no
memory movement at all. And then all of sudden the CPU spikes and the
page is rendered in a split second. This happens to any web app no
matter how simple or complex. I'm seeing the problem on a dozen
Windows 2003 boxes all built exactly the same way. Has anyone else
experienced this?
application pool on IIS 6.0. Upon the first request to an ASP.NET
page the worker process (w3wp.exe) starts up. The problem in my case
is that it takes more than 5 minutes to begin servicing requests after
the initial startup. During that agonizingly long period the process
is doing nothing...and I mean absolutely nothing...0% CPU and no
memory movement at all. And then all of sudden the CPU spikes and the
page is rendered in a split second. This happens to any web app no
matter how simple or complex. I'm seeing the problem on a dozen
Windows 2003 boxes all built exactly the same way. Has anyone else
experienced this?