CODEWITHSUNDEEP
iiscpu-usage
Sidd
Sidd

Reputation: 21

IIS application pool setting Throttle under load

One of our customers has set the application pool to throttle under load at 35%, and at times they noticed the following event

Event ID: 5210 CPU time for application pool 'abc' has been throttled.

They noticed such events show up in the event viewer log, even though the CPU utilization on the web server is not pegged high, for example < 60%

Would like to know:

• Under what condition does the event id 5210 get generated?

• How does IIS detect contention on the CPU? Is it based on a performance counter etc?

Upvotes: 2

Views: 8379

Answers (2)

chatski
chatski

Reputation: 11

This is strange question: you said you had set AppPool to ThrottleUnderLoad and set Limit to 35%. Why do you wonder when it hits the limit and generates a log record? The most common value for the throttle limit is 80%, which allows to throttle the load a little when there are too many requests and the CPU resources are not enough. I don't see sense to set the limit to 35%, this will slow web responses from your server when it has plenty of CPU time.

I suggest increasing the value. This would decrease the number of 5210 warnings.

Upvotes: 0

Jalpa Panchal
Jalpa Panchal

Reputation: 12749

The cause of the issue is there is something misconfiguration with your Application Pool.

  • open iis manager.
  • Right-click on the appropriate Application Pool and click Advanced Settings.
  • Set the Limit to 0 and Limit Action value to NoAction.

enter image description here

IIS 8.0 CPU Throttling: Sand-boxing Sites and Applications

Upvotes: 2

Related Questions