How to Tune the ASPProcessorThreadMax
- Processor:%Processor Time (for each processor)
- Active Server Pages: Requests/Sec
- Active Server Pages: Requests Rejected
- Active Server Pages: Requests Queued
- Web Service: Connections/Sec
- If the Requests Queued counter never increases and the processor(s) utilization is low, the site has more capacity than currently needed.
- If the Requests Queued counter moves up and down, and the processor(s) are running below 50 percent, this indicates that some requests are blocking, and therefore, an increase in the ASPProcessorThreadMax metabase entry may be in order.
- The Requests Queued counter grows uncontrollably along with CPU utilization. Check custom or third-party components. A component may have failed, and ASP is waiting for a response from the component.
- The Requests Queued counter grows and CPU utilization increases to an unacceptable level. Check the connectivity to databases that ASP is calling. A slow network connection, a large query, or a slow back-end computer can cause blocking.
WARNING: Modifying the metabase incorrectly can cause serious problems that mayrequire you to reinstall IIS 5.0. Microsoft cannot guarantee that problemsresulting from incorrectly modifying the metabase can be resolved. Modify themetabase at your own risk.
Run the Adsutil.vbs utility from the <%SYSTEMDRIVE%>\inetpub\adminScriptsdirectory. To re-configure the AspProcessorThreadMax metabase property, type the followingcommand:
adsutil.vbs set w3svc/AspProcessorThreadMax <NewValue>
Article ID: 238583 - Last Review: 12/05/2015 15:25:46 - Revision: 2.0
- kbnosurvey kbarchive kbinfo kbmetabase kbperformance kbsysadmin KB238583