Top 5 Feature Based IIS Server Performance Tips

At Monitis, we want your IIS maintenance and IIS monitoring to run smoothly. We are posting articles on IIS server maintenance – you can read the first article on application based IIS server performance tips and the second article on software based IIS server performace tips if you missed them. In our third article on Microsoft IIS server performance tips, we look at feature based adjustments you can make to improve IIS performance.

Adding some features in the server helps optimize the IIS7 server. Feature based tuning guidelines include putting scripts toward the end and stylesheets on top of the document, reducing DNS lookup, and other methods.

1. Optimize object cache TTL (time to live)

By default, IIS holds every object in a cache for 30 seconds before discarding it. The TTL for a dynamic environment is not required to be 30 seconds; therefore, it can be reduced. However, for a static environment, Microsoft IIS server requires TTL for more than 30 seconds. Optimizing object cache TTL helps to minimize the routing delay in networks. If TTL is set too low, valid routes are discarded.  If it is set too large, invalid routes are likely to be used.

2. Use disk striping on IIS server

Disk striping is the process of dividing a large piece of data into data blocks across multiple hard drives. Each stripe is the size of the smallest partition. It improves performance by using the hardware in all drives in tandem to access data faster. Disk striping results in the combined performance of multiple drives. Data in one drive consumes more time to read and write than data in multiple drives. It thus enhances the overall performance of the IIS web server.

3. Adjust connection timeouts

Connection timeouts conserve the lost processing resources consumed by idle connections. IIS should not hold an HTTP connection open indefinitely while a client downloads multiple files. By enabling connection timeouts, IIS web server enforces the timeouts at the connection level.

By default, Microsoft IIS server 6.0 is configured to terminate a connection after 120 seconds of inactivity. This is not ideal for all organizations. Usually shorter timeout periods increase the IIS server’s performance, but if a client’s connection is terminated prematurely, performance will degrade.

4. Throttling Bandwidth

Throttling is a process of keeping server resources available and responsive. It enables a direct correlation between the number of connections and bandwidth utilized or required. IIS 7 offers various ways to throttle resources, from bandwidth to connection timeouts and limits.

In case the internet connection or network used by the IIS web server is also used by other services. such as email or news, it requires limiting the bandwidth used by the IIS server so it is available for those other services.

Throttling the number of connections one website receives prevents it from using too many connections or IIS server resources. In addition, it also prevents other websites hosted on the IIS server from being affected.  Enabling bandwidth throttling on IIS definitely improves performance.

5. Limit Connections

Connection limits limit the number of simultaneous client connections to websites and the IIS web server. It boosts IIS 6 performance by conserving memory and protecting against malicious attacks designed to overload the web server with thousands of client requests, such as a DDoS attack.

We hope you were able to utilize these IIS management tips for your IIS server installation. Stay tuned the Monitis blog for new performance management articles.

See also

Top 4 Software Based IIS Server Performance Tips

Top 8 Application-Based IIS Server Performance Tips