There were few of article on the internet talking about this topic IIS CPU throttling in broderses that it will ensure application pool will not exceed the cpu limit over a period of time. However no one quite sure how CPU Limit Action Throttle works internally. I am trying find answers.
Set the cpu limit to 10000 (10%), Limit Action Throttle, the Limit Action to 00:05:00 (5mins). Now if my web site running on single application pool, uses the 10% cpu in the first 3 minutes what will happen for the next 2 mins ? IIS is going to stop accepting any more connections similar to KillW3wp case?
What is the minimum Limit interval I can set for example can I set 5 or 10seconds ?so that the cpu is limited in a granular level so that the one application pool will not hog the resouces continously for minutes.
some blogs have information about IIS sending 500 error in case of the limit actino is KillW3wp (http://blogs.iis.net/shauneagan/archive/2012/03/15/cpu-throttling-iis-7-vs-iis-8.aspx)
How is IIS is doing the throttling (or algorithm?) is this related process priority switching in the background?