• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Health Monitoring IIS CPU

Jonas N

Basic Pleskian
Plesk Certified Professional
Hey Guys and gilrs.....

I hope that someone can help me with a problem that i have !
According to The health monitoring iis cpu usage

Is this normal that it spikes to 180 % ??
iis cpu.PNG

If not.! how do i troubleshoots this best ?

Best regards

Jonas Nordin
 
The WWW service monitors the health of worker processes by periodically pinging them to determine their responsiveness. If a worker process fails to respond to a ping (for example, the worker process might not have available threads to process the incoming request), the WWW service either terminates the worker process and creates another worker process to replace it, or releases the worker process but lets it continue to run. You can configure IIS to perform a specified action when an unhealthy worker process is released — for example, you can specify that IIS attach a debugger to a released worker process.
Additionally, the WWW service maintains a communication channel to each worker process and can detect a drop in the communication channel, which indicates a worker process failure. When a worker process fails of its own accord, the WWW service starts another worker process in its place, provided the application pool does not go into rapid-fail protection.
 
The WWW service monitors the health of worker processes by periodically pinging them to determine their responsiveness. If a worker process fails to respond to a ping (for example, the worker process might not have available threads to process the incoming request), the WWW service either terminates the worker process and creates another worker process to replace it, or releases the worker process but lets it continue to run. You can configure IIS to perform a specified action when an unhealthy worker process is released — for example, you can specify that IIS attach a debugger to a released worker process.
Additionally, the WWW service maintains a communication channel to each worker process and can detect a drop in the communication channel, which indicates a worker process failure. When a worker process fails of its own accord, the WWW service starts another worker process in its place, provided the application pool does not go into rapid-fail protection.
 
The WWW service monitors the health of worker processes by periodically pinging them to determine their responsiveness. If a worker process fails to respond to a ping (for example, the worker process might not have available threads to process the incoming request), the WWW service either terminates the worker process and creates another worker process to replace it, or releases the worker process but lets it continue to run. You can configure IIS to perform a specified action when an unhealthy worker process is released — for example, you can specify that IIS attach a debugger to a released worker process.
Additionally, the WWW service maintains a communication channel to each worker process and can detect a drop in the communication channel, which indicates a worker process failure. When a worker process fails of its own accord, the WWW service starts another worker process in its place, provided the application pool does not go into rapid-fail protection.


Hmmm oki, what would be the best way, we have only moved about 28 client and allready have this problem...
How to solve it?

Best regards
Jonas
 
No its not VM.

Hp Proliant DL380 G6
Intel(R) Xeon(R) CPU E5520 @ 2.27GHz Intel64 Family 6 Model 26 Stepping 5 ~2266MHz
10 Gig Ram.
New.PNG

It`s geeting worse... = (
 
You can also check the perfmon tool to get more information on these events. Alternatively, check the event manager too for any errors or warning that IIS may have given related to any application pool having to use more resources or something similar such events.

What does these 2 show?
 
I too am experiencing high IIS usage alerts from Plesk. Not sure what's causing it nor how to stop it. Any suggestions will be gratefully accepted. And yes it's a VM running Windows Server 2012 R2.

High IIS CPU usage.jpg
 
Back
Top