>> 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.
Sounds very promising, can't wait to see your work :D -- Kyle ------------------------------------------------------------------------------ _______________________________________________ Nagios-users mailing list Nagios-users@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
