Nagios active check performance limits

[Andreas Ericsson]

Gaspar, Carson wrote:
> As per my original mail, 13.5 checks / second (with each check being a
> dumb sleep .5 secs, return OK C program) on an HP DL385 G1 2 x dual core
> opteron 2.4 GHz (so 4 cores total) running RHEL4U4.
> 

Yes, but it should be possible to run up to sysconf(_SC_OPEN_MAX) / 2 such
checks per second (minus a few for stdin, stdout, logfiles, etc...). On
most systems, that means between 500 and 1000 active checks per second.

I have a program which does just that, although it's far too stupid to
take such things as scheduling windows into account, ofcource ;-)

> We don't use _any_ active checks on our prod system. I was just
> generating numbers for my talk so I could do more than wave my hands and
> say active checks were "slow", based on my decision to dump them back in
> the 1.x days...
> 
> Once the USENIX folks get the talk video up, I'll post a link to it
> here. And with any luck, I'll get approval to release my source by the
> end of the year (I have approval in principal, but I still need to pass
> code review).
> 

If the source is based on Nagios code, it's illegal to stop you from
releasing it. One of those nifty things about GPL.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/