Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been looking at enabling the CPU Limit for a website.
Under Advanced Settings for the appropriate Application Pool I set
CPU Limit: 95000
Limit Action: NoAction
Limit Interval: 5

After leaving this for a night, I checked the event logs to see how often that the worker process would have been recycled. To my horror it would have done so every few minutes, implying the server was maxed out for much of the night which is incorrect, logged total cpu usage never gets over 50%.

Using Task manager, Resource Manager and PerfMon during the day and adjusting the above values, they all agreed that overall cpu usage averaged 13%, however PerfMon differed when you looked at the individual process cpu usage (counter: Process\% Process Time(w3wp) reporting 30%-40% average. This counter managed to reach the high 300% which after reading here is because its a sum of all usage across all cores and not normalised like the other counters.
Now my problem appears that the IIS CPU limiting bases its decision on this counter and thus wants to wrongly recycle the process.

This is a windows 2008 x64 standard edition installation on bare metal, quad core, IIS is the only role installed. I've configured both the BIOS and windows power management for performance as I wondered if the ramping up/down of the cpu speed might have affected this but it hasn't.

I don't need to diagnose high cpu usage, we just want to have the process correctly recycled if it ever reaches a high level.
I assume I must have missed some dependency setting elsewhere, and now at a loss as how to correctly implement this cpu limiting.

share|improve this question

To get a similar number in Perfmon, you need to divide the output record you get in Perfmon by the number of CPU's on the System. Note that Perfmon and TaskManager use different ways to collect that information.

For example - I have a VM with 3 vCPU's - the maximum a process can get to is 300%, so I simply divide the Perfmon record of that process by 3.

share|improve this answer
I understand this, my problem is that IIS/WAS appears to use this value when you configure cpu limits for the app pool, but only lets you enter values 0-100% – snoopy-do Jan 19 '13 at 21:20
I think you should look at WSRM. That's what I use to limit processes. It's a role you add from Server Manager. Here are some useful links:…… – Idan Jan 20 '13 at 5:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.