High latency issues on Nagios 3.2.1

[Cary Petterborg]

We are currently working towards migrating from Nagios 2.7 to 3.2. We have 37,000+ services and 3,000+ hosts. We have a test environment with an 8 CPU system running Nagios 3.2.1 and we are getting high latency of 330+ seconds. The configuration has the large installation tweaks turned on and max_concurrent_checks=10000000. The load average on the system is around 3 to 4, but the CPU utilization is less then 50% on the average, with peaks of 80+% that might last 1 second about every 10 or 15 seconds.

So my question is this - Is there something that we can do to lower the latency and increase the CPU utilization? Is there some limiting factor with our configuration that we need to tweak, or is it just too many checks for the main Nagios process to handle in the time frame, or something else?

I can provide any information that would make it possible to lower the latency.

Thanks!!


Cary Petterborg
ICS Monitoring
The Church of Jesus Christ of Latter-day Saints
Office Phone: 801-240-8267
Email:  petterborgca at ldschurch.org


 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.



------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null