Use IIS 5.0 to adjust the art and science of a Web server (Appendix 1)

Appendix 1: Performance Settings
You can adjust the IIS Metabase content and registry settings to adjust the performance of your WEB server. If you plan to change the registry, do not use Registry Editor unless no other method is available. Registry Editor ignores the standard security settings provided by the system administration tools. These security settings prevent you from entering conflicting setting values, or may degrade performance or damage the system's settings. Directly editing the registry can result in serious and unpredictable consequences that can cause the system to fail to start, and you must reinstall Windows 2000. The same situation can occur with adsutil utilities (found in the inetpubadminscripts directory) to change IIS. To set or customize Windows 2000 and IIS 5.0, use either Control Panel or Microsoft Management Console (MMC) as much as possible.
Metabase settings
This list includes the most important metabse settings used to adjust the WEB server. Use the ADSI interface to get and change them. Most of these settings will not take effect until the WEB service is restarted. For information, see the section describing the IISReset utility.
Appallowdebugging-This property specifies whether ASP debugging is enabled on the server. If enabled, the IIS application thread is serialized, which means that each application can execute only one thread at a time. This can have a detrimental effect on the performance of the WEB server. You can set this property to FALSE on all production servers (default).
aspallowsessionstate-The default value is TRUE. Adjusting it to FALSE can result in higher performance. Once changed, the developer must explicitly replace this setting on the page that needs to use the "validity" object. To change the default settings on a single page, developers can use the <% @EnableSessionState =false%> at the top of the page. To change this option, be sure to notify the developer.
aspbufferingon-The default value is TRUE. The default behavior of this property is to allow all output from the application to be collected in the buffer before the buffer is transferred to the client browser. If this property is set to FALSE, the output from the ASP script file is written to the client browser when the client is using the browser. You must determine that this property is set to TRUE on all production environment Web servers. For more information, see the "Adjustments and troubleshooting Recommendations" section of this article.
AspThreadGateEnabled (default is FALSE) and AspProcessorThreadMax (default is 25)-When you set aspthreadgateenabled to TRUE, thread routing is enabled and IIS 5. 0 dynamically changes the number of worker threads to respond to changing workloads. IIS allows the maximum number of worker threads per ASP process to be aspprocessorthreadmax multiplied by the number of CPUs on your server. Lower this value and monitor performance. If the performance is reduced, please recall the AspProcessorThreadMax value. For information, see the Threading section in this article.