Nagios 3.2 and max_concurrent_checks=0

[Cary Petterborg]

I'm doing some testing for migrating our installation to Nagios3.2. The test server is running 3.2 on an 8 CPU box with 34,000 active service checks and 3,000 active host checks. The initial configuration file had max_concurrent_checks=0, but latency was about 9,000 seconds. I changed it to max_concurrent_checks=200 and the latency went down to about 7,000 seconds. I then set it to 2,000 and the latency dropped to about 200 seconds. I currently have it set to 100,000 and latency has not changed from about 200 seconds.

>From all the documentation I have seen, if max_concurrent_checks is set to zero, there should be no limit on the number of concurrent checks, but this doesn't appear to be the case. Is there some other part of the configuration that I'm missing which would make max_concurrent_checks=0 be limited instead of unlimited?


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.



------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
_______________________________________________
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