Article ID: 238583
You may need to tune the Active Server Pages (ASP) queue if ASP scripts make more requests to a Component Object Model (COM) component than the component can handle. All calls made beyond the component's capacity are put into the ASP queue. This is called blocking. Blocking can also occur if threads are waiting for a response from an external resource, such as a database. When you use ASP under heavy load, the processor utilization should be above 50 percent or an acceptable level.
To get the statistics needed to tune the ASPProcessorThreadMax metabase property, observe the following System Monitor counters at peak load time using a one-second chart interval:
WARNING: Modifying the metabase incorrectly can cause serious problems that may require you to reinstall IIS 5.0. Microsoft cannot guarantee that problems resulting from incorrectly modifying the metabase can be resolved. Modify the metabase at your own risk.
Run the Adsutil.vbs utility from the <%SYSTEMDRIVE%>\inetpub\adminScripts directory. To re-configure the AspProcessorThreadMax metabase property, type the following command:
Where <NewValue> is the number of threads that ASP should use per processor. This sets the value at the Master WWW Properties level where it is inherited by all new Web applications and all existing applications that have not explicitly set a different value for AspProcessorThreadMax. NOTE: ASPProcessorThreadMax should not be changed unless blocking is occurring. If the Total Queue Length grows and the Processor Time grows to an unacceptable level, troubleshoot custom components or database connections.
Article ID: 238583 - Last Review: June 19, 2014 - Revision: 2.0