You are currently offline, waiting for your internet to reconnect

Compiling Large ASP Pages Can Take 100% of CPU Time

This article was previously published under Q193831
This article has been archived. It is offered "as is" and will no longer be updated.
We strongly recommend that all users upgrade to Microsoft Internet Information Services (IIS) version 6.0 running on Microsoft Windows Server 2003. IIS 6.0 significantly increases Web infrastructure security. For more information about IIS security-related topics, visit the following Microsoft Web site:
When an ASP file is requested for the first time, it must be compiled.Normally, this will only last a short time. However, if the ASP andassociated include files are large, Internet Information Server (IIS) canstay at 100 percent CPU usage, which prevents the server from servicingclient requests.
ASP is a run-time interpreted environment designed for small files. Eachscript block in the ASP file is parsed separately. Processing these blocksis CPU intensive, especially when there are hundreds of disparate scriptblocks.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

To work around this problem, design the ASP to use a single script blockinstead of individual blocks. For example:
<html tag> some text </html tag> <% = variableName %>
<html tag> some text </html tag> <% = CallToFunction(param1, param2) %>

takes longer to compile than:
Response.Write ("<html tag> some text </html tag> " & variableName)
Response.Write ("<html tag> some text </html tag> " &
CallToFunction(param1, param2))

Multiple records can be displayed using ADO and a query loop. This reducesthe amount of redundant script blocks and make the compile much faster.
Microsoft has confirmed this to be a problem in Internet InformationServer version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
IIS hotfix hot fix qfe quick fix engineering patch

Article ID: 193831 - Last Review: 10/26/2013 13:19:00 - Revision: 5.0

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB193831