Here are eight ways to improve the efficiency of IIS 5.0 Web server execution:
1. Enabling HTTP persistence can improve the efficiency of 15~20% execution.
2. Not enabling logging can improve the efficiency of 5~8% execution.
3. The use of a [stand-alone] handler can cost 20% of its execution efficiency.
4. Increasing the number of saved documents for cache memory can improve the efficiency of activeserver pages.
5. Do not use CGI program
6. Increase the number of IIS 5.0 computer CPUs.
7. Do not enable the ASP debugging function.
8. Static Web pages are compressed by HTTP, which can reduce the transmission volume by 20%.
Briefly described below
1. Enable HTTP to continue to function
When HTTP persistence is enabled (keep-alive), the connection between IIS and the browser is not disconnected and can improve execution efficiency until the connection is disconnected when the browser is closed. Because the "keep-alive" state is maintained, a new connection is not required on each client request, so the efficiency of the server is improved.
This feature is an HTTP 1.1 preset feature, and HTTP 1.0 plus the Keep-alive header can also provide an ongoing function of HTTP.
2. Enabling HTTP's continued role can improve the efficiency of 15~20% execution.
How do I enable HTTP to continue? The steps are as follows:
In Internet Services Administrator, select the entire IIS computer, or Web site, on the home directory page of content, and check the HTTP persistence option.
3. Do not enable logging
Not enabling logging can improve the efficiency of 5~8% execution.
How do I set a record that is not enabled? The steps are as follows:
In Internet Services Administrator, select the entire IIS computer, or Web site, on the home directory page of content, and uncheck the Enable logging option.
Set up a non-independent handler
Using a [standalone] handler loses 20% of the execution efficiency, where the term "standalone" means that the Application Protection option for the home directory, virtual directory page is set to [High (independent)]. Therefore, when application protection is set to low (IIS handlers), the execution is more efficient and the setting screen is as follows: