Full Throttle Nagios

[Max]

Really look forward to seeing this code - this is the process pool code, yes?

On 5/19/10, Andreas Ericsson <ae at op5.se> wrote:
> There are several tweaks one can do to make Nagios more or less saturate the
> CPU, but none of them are enough if the number of checks rise above a
> certain
> level. We've noticed that we can run about 60K service-checks so long as we
> don't have many state-changes in the network. That's not nearly good enough,
> so it will be improved.
>
> Work is under way to revamp the Nagios check handling though. It will get
> better, but it's a series of large patches that need to be thoroughly tested
> before they get released.
>
> I'll holler when I have them in a testable state, since I guess a lot of
> people would be quite interested in trying out the new checking engine I'm
> working on. If it works as good as it seems to, it should alleviate a lot
> of performance issues.
>
> --
> Andreas Ericsson                   andreas.ericsson at op5.se
> 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.
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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
>

------------------------------------------------------------------------------

_______________________________________________
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