David
Sun Nov 26 03:27:26 CST 2006
By default, .html or .jpg is served by the IIS Static File Handler,
which is very fast.
The common explanations for what you see are either:
1. you configured ASPNET_ISAPI.DLL as a wildcard application mapping so
that it is involved in serving ALL resource types, including .html or
.jpg. Thus, you see the ASP.Net 10 second initialization hit, even on
an HTML file that is ultimately not handled by ASP.Net.
2. you configured some ISAPI Filter or ISAPI Extension as wildcard
application mapping which has a 10 second startup perf hit. For
example, some ISAPIs take a long time to startup, allocate memory,
warmup caches, etc -- just like ASP.Net initialization.
I can only say that the behavior does not sound like a "new" or
"default" Windows Server 2003 machine with IIS6 - it sounds like an
arbitrarily customized installation of Windows Server 2003 that you
have access to.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
K. Abit wrote:
> On a new Win 2003 Server with IIS6, it typically takes 10 seconds to serve
> an HTML file. Even when I point the browser to just an image, it takes 10
> seconds. But once I've pulled something from the site, it then runs
> fast/normally for subsequent pages. Why? It is part of the shared site
> pool. I understand that with ASP.NET applications, it has to compile the
> app the first time, but here I am talking about a ".html" or ".jpg" file
> that takes this long. Again, why?