{"id":2619,"date":"2016-10-30T11:10:42","date_gmt":"2016-10-30T18:10:42","guid":{"rendered":"http:\/\/www.coretechnologies.com\/blog\/?p=2619"},"modified":"2016-10-30T11:10:42","modified_gmt":"2016-10-30T18:10:42","slug":"version-5-3-monitors-multiple-cpus","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/service-protector\/version-5-3-monitors-multiple-cpus\/","title":{"rendered":"Windows Service Protector 5.3 Monitors Multiple CPUs"},"content":{"rendered":"
\"New<\/div>\n

If you are responsible for keeping a CPU-hogging<\/a> Windows Service running all the time, then we have some great news! Service Protector<\/a>, our time-saving administrative tool that helps any Windows Service achieve 100% uptime, is now able to monitor processor use across all<\/b> your server’s CPUs.<\/p>\n

Previous versions of Service Protector would only monitor a single CPU\/Core. This approach fit with the vast majority of today’s popular windows services that run entirely on one CPU, but it was inadequate for newer, performance-hungry services designed to make use of all a server’s CPUs. This release addresses that deficiency by detecting “runaway” services consuming too many cycles across all the CPUs.<\/p>\n

How to Activate Windows Service “CPU Hog” Detection Across All Processors<\/b><\/h2>\n

To identify and automatically restart a misbehaving windows service that ties up multiple CPUs, simply check the Average over all CPUs (instead of only one)<\/b> box when configuring Service Protector’s Monitor tab:<\/p>\n

\n
\n\"Catch<\/a>\n<\/div>\n

<\/p>\n

With the above setting, a service running on a 4-CPU machine that consumes over 95% of all processing power would be automatically restarted by Service Protector.<\/p>\n

Enjoy!<\/p>\n