Sometimes we may find the ASP requests are very slow because of too many requests queued. Then we can modify the Metabase property of ASPProcessorThreadMax to improve the performance. For more information about how to tune this property, please refer to the following articles
Based on the ASPProcessorThreadMax definition, it seems this property can be set on website level or virtual directory level. However, after some experiments I find this property ONLY works when we set on W3SVC level as below.
adsutil.vbs set w3svc/AspProcessorThreadMax <NewValue>
Besides this value, we can also set the EmulateMTSBehavior value to 1 so that the worker process can host at most 100 concurrent ASP requests.
Value name: EmulateMTSBehavior
Data type: REG_DWORD
Value data: default is 0
By setting this parameter to 1, it will set the max threads number of STAThreadPool to 100, so this setting can also affect the other STA COM+ applications. Furthermore, if you set the EmulateMTSBehavior value, the AspProcessorThreadMax setting will be ignored. And the EmulateMTSBehavior setting won’t aware the processor number, this means the process can only starts at most 100 STA threads no matter how many processors you have.
We can also let ASP run in MTA by setting AspExecuteInMTA value. If your COM components are primarily free-threaded or both-threaded, running the ASP threads as MTA can improve performance significantly.