H
HridayDutta
Application pools provide an isolation between different web application in Internet Information Services (IIS) by allowing you to manage the resources, recycling, and performance per application. Control of CPU usage is going to be one of the most critical factors in the performance and management of an application pool. IIS includes a dedicated section under ApplicationPool -> Advance Settings for the management of CPU. it provides varied settings that enable you to optimize the utilization of the CPU so that a particular server resource does not become dominated by one application. This article will dive into the CPU settings for an ApplicationPool, explaining each option and its configuration.
In the application pool advance settings, the CPU section consists of many important configurations to control and monitor CPU usage. They are as follows -
#1 Limit (percent)
The Limit (percent) setting allows you to specify the maximum percentage of CPU that a particular application pool can consume. The percentage is based on the total CPU capacity available on the server, where 100 represents the total CPU power. Setting the value of this property to 0 disables limiting the worker processes to a percentage of CPU time. And if the limit set by the CPU Limit is exceeded, an event is written to the event log and an optional set of events can be triggered as determined by the CPU Limit Action property. For multi-core processors, the limit applies to the total CPU time across all cores. For instance, on a 16-core machine, setting the limit to 25% ensures that the application pool cannot use more than the equivalent of 4 core.
#2 Limit Action
This setting specifies the action IIS will take when the application pool exceeds the configured CPU limit percent. You can choose any action form the list below.
NoAction: IIS will monitor CPU usage but will not take any corrective action if the application pool exceeds the CPU limit. Only an log entry is generated in event logs.
KillW3WP: IIS terminates the worker process (w3wp.exe) associated with the application pool when CPU usage exceeds the limit. The application pool is shut down for the duration of the reset interval and a log entry is generated in event log.
Throttle: IIS will attempt to slow down the application by delaying its access to CPU resources when it exceeds the limit. This action helps ensure that other application pools or processes have sufficient CPU resources.
ThrottleUnderLoad: This option allows the application to exceed the CPU limit when the server is under low load but throttles it when the server experiences higher demand.
#3 Limit Interval (minutes)
The Limit Interval determines the time period (in minutes) over which IIS measures CPU usage. When the number of minutes since the last process accounting reset reaches the value defined by this property, IIS will reset the CPU timers for both logging and limit intervals. Setting this property to 0 disables CPU monitoring.
#4 Processor Affinity Enabled
The Processor Affinity Mask property forces the worker process serving this application pool to run on specific CPUs based on the Processor Affinity Mask value.
#5 Processor Affinity Mask
This setting allows you to restrict the application pool to run on specific processors (or CPU cores). The affinity mask is a bitmask that specifies which processors the application pool should run on. You can use any available CPU Affinity Mask calculator online, or you can calculate it manually. If you'd like a detailed explanation on how to calculate the CPU Affinity Mask, feel free to leave a comment, and I'll write a follow-up article on this topic.
#6 Processor Affinity Mask (64-bit option)
It specifies the high-order hexadecimal mask for a 64-bit machine. This setting provides the same functionality as the Processor Affinity Mask but extends support for systems with more than 32 processors.
Generally, it’s safer to use Throttle or ThrottleUnderLoad to maintain system stability without abruptly terminating applications. KillW3wp is a more aggressive approach and should be used with caution, as terminating the worker process can lead to application downtime and a poor user experience. Also, the Processor Affinity Mask is rarely used unless you are dealing with specific performance tuning scenarios or licensing restrictions on multi-core processors. The modern CPU scheduling mechanisms in the OS typically handle processor assignment more efficiently.
Managing CPU settings within IIS application pools is crucial for maintaining performance, stability, and efficient resource utilization. Configuring CPU limits and actions properly, you can prevent over-consumption of server resources by any one application. This ensures fair resource distribution across other applications running on the same server. Properly managing CPU settings contributes to overall server health, making your IIS environment more resilient and adaptable to growth.
Continue reading...
Overview
In the application pool advance settings, the CPU section consists of many important configurations to control and monitor CPU usage. They are as follows -
- Limit (percent)
- Limit Action
- Limit Interval (minutes)
- Processor Affinity Mask
- Processor Affinity Mask (64-bit option)
#1 Limit (percent)
The Limit (percent) setting allows you to specify the maximum percentage of CPU that a particular application pool can consume. The percentage is based on the total CPU capacity available on the server, where 100 represents the total CPU power. Setting the value of this property to 0 disables limiting the worker processes to a percentage of CPU time. And if the limit set by the CPU Limit is exceeded, an event is written to the event log and an optional set of events can be triggered as determined by the CPU Limit Action property. For multi-core processors, the limit applies to the total CPU time across all cores. For instance, on a 16-core machine, setting the limit to 25% ensures that the application pool cannot use more than the equivalent of 4 core.
#2 Limit Action
This setting specifies the action IIS will take when the application pool exceeds the configured CPU limit percent. You can choose any action form the list below.
NoAction: IIS will monitor CPU usage but will not take any corrective action if the application pool exceeds the CPU limit. Only an log entry is generated in event logs.
KillW3WP: IIS terminates the worker process (w3wp.exe) associated with the application pool when CPU usage exceeds the limit. The application pool is shut down for the duration of the reset interval and a log entry is generated in event log.
Throttle: IIS will attempt to slow down the application by delaying its access to CPU resources when it exceeds the limit. This action helps ensure that other application pools or processes have sufficient CPU resources.
ThrottleUnderLoad: This option allows the application to exceed the CPU limit when the server is under low load but throttles it when the server experiences higher demand.
#3 Limit Interval (minutes)
The Limit Interval determines the time period (in minutes) over which IIS measures CPU usage. When the number of minutes since the last process accounting reset reaches the value defined by this property, IIS will reset the CPU timers for both logging and limit intervals. Setting this property to 0 disables CPU monitoring.
#4 Processor Affinity Enabled
The Processor Affinity Mask property forces the worker process serving this application pool to run on specific CPUs based on the Processor Affinity Mask value.
#5 Processor Affinity Mask
This setting allows you to restrict the application pool to run on specific processors (or CPU cores). The affinity mask is a bitmask that specifies which processors the application pool should run on. You can use any available CPU Affinity Mask calculator online, or you can calculate it manually. If you'd like a detailed explanation on how to calculate the CPU Affinity Mask, feel free to leave a comment, and I'll write a follow-up article on this topic.
#6 Processor Affinity Mask (64-bit option)
It specifies the high-order hexadecimal mask for a 64-bit machine. This setting provides the same functionality as the Processor Affinity Mask but extends support for systems with more than 32 processors.
Key Points
Generally, it’s safer to use Throttle or ThrottleUnderLoad to maintain system stability without abruptly terminating applications. KillW3wp is a more aggressive approach and should be used with caution, as terminating the worker process can lead to application downtime and a poor user experience. Also, the Processor Affinity Mask is rarely used unless you are dealing with specific performance tuning scenarios or licensing restrictions on multi-core processors. The modern CPU scheduling mechanisms in the OS typically handle processor assignment more efficiently.
Conclusion
Managing CPU settings within IIS application pools is crucial for maintaining performance, stability, and efficient resource utilization. Configuring CPU limits and actions properly, you can prevent over-consumption of server resources by any one application. This ensures fair resource distribution across other applications running on the same server. Properly managing CPU settings contributes to overall server health, making your IIS environment more resilient and adaptable to growth.
Continue reading...