It’s good to know it would be released, but it runs hotter than needed and wastes electricity. Is it something ridiculously complicated to fix or something rarely this pronounced because of the number of checks we run?
Peter Anderson Manager, Network Services, ITS Cuyahoga Community College Tri-C(R) Where futures begin www.tri-c.edu From: Servers Alive Discussion List [mailto:salive@woodstone.nu] On Behalf Of Dirk Bulinckx Sent: Wednesday, July 11, 2012 12:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] CPU usage very high; culprit? The wait loops (wait for a response from the remote system) can cause this behaviour. However if other processes will "ask" for CPU time they will get it from the OS. Dirk Bulinckx Servers Alive - http://www.woodstone.nu (http://www.woodstone.nu/) StellarDNS (DNS Hosting) - http://www.stellardns.com (http://www.stellardns.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:salive@woodstone.nu] (mailto:[mailto:salive@woodstone.nu]) On Behalf Of Anderson, Peter Sent: Wednesday, July 11, 2012 5:46 PM To: Servers Alive Discussion List Subject: [SA-list] CPU usage very high; culprit? When checks are running (large collection of pings, service checks, disk space, even log), comSAWrapper.exe has 5 or more threads, each running 15-20% CPU (single CPU, 8 core). On the previous hardware this was only 2 cores and the server was often unresponsive. Now it still gets quite slow. Other servers running SA with just ping/snmp checks don’t display this behavior. Is this most likely the result of the service checks, event log checks, or something else? I hesitate to turn off all the checks of a certain type if somebody else has already seen this. I am running the most recent plugin versions for each. Thanks, Peter Anderson Manager, Network Services, ITS Cuyahoga Community College Tri-C(R) Where futures begin www.tri-c.edu (http://www.tri-c.edu) To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu (mailto:salive@woodstone.nu) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
