On 04/16/2010 05:36 PM, Adam Augustine wrote:
> I think what he is saying is that setting it to zero limited the
> number of checks to 200, while increasing it to 1,000,000 caused it to
> execute more than 200, which would seem backwards if 0 basically means
> "do as many as you possibly can" (based on CPU).
>
Amount of checks run simultaneously is rarely a case of CPU limitations,
but rather of the amount of open file-descriptors. I'm working on a
possible solution to this, implementing Jean Paul Gabès' plan of utilizing
a pool a worker processes whose sole purpose is to execute checks, which
hopefully will alleviate all performance issues.
> This would indicate that max_concurrent_checks=0 is limiting it to
> some number rather than using all the CPU possible, which sounds like
> a bug.
>
Yes. I expect this has to do with the smart check interleave factor and
wildly different check_interval variables. Nagios does something wrong
there, but it's unusual enough (and mild enough) for most people that
noone has bothered to correct it yet.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]