Configuring idle timeouts and recycle schedules for application pools in IIS optimizes performance and resource management. 1. Idle timeout is used to close the application pool when there is no request. The default is 90 minutes, which is suitable for low access scenarios. If the settings are too short, it may cause the first access delay. It is recommended to adjust according to the traffic. If the intranet system is set to 30 minutes, the external network will remain the default or longer. The operation steps include opening the IIS manager, selecting the application pool, and modifying the "Idle timeout (minutes)". 2. Regular recycling can release resources during low peak periods and prevent leakage. It is commonly set to 2 a.m. Enable "Overlapping Recycling" to reduce interruptions; the setting method is to add recovery time points in "Advanced Settings". 3. It is recommended to analyze the request frequency and resource usage in combination with logs and monitoring, and continuously optimize the configuration to ensure a balance of stability and efficiency.

Configuring idle timeouts and recycling plans for application pools in IIS is an important step in optimizing server performance and resource management. Setting these parameters rationally can avoid resource waste while ensuring applications respond quickly when needed.

1. Understand the Idle Timeout

Idle timeout refers to the fact that when an application pool does not have any request processing within a specified time, IIS will automatically close the application pool to save system resources.

• Default value : 90 minutes
• Applicable scenarios : suitable for applications with low access volume, such as internal management systems or test environments.
• Note : If the idle time is set too short, it may cause delays when the user first access is due to the application that needs to be restarted.

It is recommended to adjust this value based on actual business traffic. For example, the enterprise intranet system can be set to 30 minutes, while external service websites are recommended to keep the default or longer.

Operation steps:

• Open IIS Manager
• Select the corresponding application pool
• Click "Advanced Settings"
• Modify the "Idle Timeout (Minutes)" item

2. Set up a Recycling Schedule

In addition to recycling based on idle state, you can also set up a timed recycle application pool. This helps free up memory, restart processes that may have problems, and prevent resource leaks caused by long-term operation.

• Common settings : Recycling is performed at 2 a.m. every day
• Advantages : Restart can be completed during the peak period without affecting the user experience
• Note : If there is an ongoing request during recycling, the operation may be interrupted. It is recommended to use it in conjunction with the "request queue" mechanism

The setup method is as follows:

• Find Recycle in Advanced Settings in Application Pool
• Expand "Recycling Time (Time-based Recycling)"
• Add one or more time points, such as 02:00:00

If your application has extremely high availability requirements, consider enabling the "overlapping recycling" function to allow new and old work processes to alternately run and reduce interruptions.

3. Adjust with logs and monitoring

Relying solely on default settings may not meet the needs of complex businesses. It is recommended to continuously optimize through the following methods:

• View request frequency in IIS logs and analyze peak and trough time periods
• Use Performance Monitor (PerfMon) to observe memory usage and CPU usage
• Use event viewer to track application pool recycling events to confirm whether they are frequently triggered

If you find that the application pool is recycled multiple times a day, but there is no significant performance degradation, it may be that the setup is too aggressive; on the contrary, if it is not recycled once a few days, you may want to consider introducing regular recycling to free up resources.

Basically that's it. Configuring Idle Timeout and Recycling Schedule is not complicated, but it is easy to ignore details. As long as you adjust flexibly according to the actual load, you can find a balance between stability and resource efficiency.

The above is the detailed content of Configuring Idle Timeout and Recycling Schedules for IIS Application Pools. For more information, please follow other related articles on the PHP Chinese website!