IIS6 + ASP.NET : Performance Problems

By-design.

What is happening is that IIS6 recycles worker processes if they idle
(configurable timeout) to conserve resources for active sites. ASP.Net
pages require loading the CLR to run, which is a very expensive operation.

Everytime that you start up a new w3wp.exe to run ASP.Net pages, the CLR
needs to be loaded, which is taking much of the 20 seconds you observe.

Since you left IIS6 configured to recycle worker processes by idle timeout,
the behavior you observe is by-design. The default values for IIS6 work
very well for ASP/COM/ISAPI applications, but they do not work well for
ASP.Net applications.

It is recommended that you create a new Application Pool for all ASP.Net
applications and assign them to it. This Application Pool should have all
recycle settings disabled except for Private Memory, which should be set at
60% Physical RAM. Everything else should be left as-is.

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Maik" <maik[at]maik[NOSPAM]siegel.de> wrote in message
news:%23p$iPDFtEHA.2800@tk2msftngp13.phx.gbl...
In the past days, i have programmed a complete site using asp.net .
I put it on my server and most worked like expected. After correcting the
last erros, i mentioned tha every time, when the site unvisted for some
minutes, it takes lot of until the site is loaded.

When i click several links in a short time, everything works fine - and if i
pause 10 minutes, the first loading lasts nearly 20 second. During thing 20
seconds, the cpu usage of the server is relativ high.
Is the server compiling the asp.net pages every time ?
And how can i prevent him from doing this ?

--
Best Whishes, Maik


Knowledge is Power
Replace [at] and remove [NOSPAM] to get Email-Adress
 >> Stay informed about: IIS6 + ASP.NET : Performance Problems