次の方法で共有

IIS 6.0 Performance Tuning (2)

  • [アーティクル]

Web server administrators often monitor their Web servers to create a performance baseline. A performance baseline is a collection of data that indicates how the servers are performing when everything is running smoothly. Before making changes to their servers in a production environment (for example,. rolling out a new version of a Web application or hardware changes) administrators tune their servers in a test environment to achieve the established performance baseline. By tuning their servers in this way, they maximize throughput and minimize Web application response times, which create a better experience for clients accessing their Web servers.

It sounds like easy to do. In reality, many administrator are too busy. They didn't consider the tuning. They don't even test performance before deploying to production environment.
Remember this. Performance tuning is a key solution to improve response time.

•

Using HTTP Compression: Describes how to improve performance between client computers and servers by reducing file sizes before the files are sent to the client computer. Reducing the file size as described here is referred to as compression.
•

Enabling HTTP Keep-Alives: Describes how to use HTTP Keep-Alive requests to maintain an open connection.
•

Limiting Connections: Describes how to set limits on the number of connections allowed to a Web server.
•

Setting Connection Timeouts: Describes how to set connection time-out values on a Web server.
•

Throttling Bandwidth: Describes how to change the bandwidth used by a Web server and individual Web sites.
•

Enabling CPU Monitoring in IIS 6.0: Describes how to monitor and stop problematic applications.
•

Configuring Application Pool Queue-Length Limits: Describes how to limit the number of requests IIS stores in any application pool queue so the requests do not grow to such a large size as to exhaust server resources.
•

Scalability: Provides information and links to detailed resources about scalability.

[Refered from microsoft.com]

Comments