> Hi list,
>
> I think there is something missing in the PERFORMANCE SUGGESTIONS section of
> the scheduling test (-s).
>
> I used to update the status file as results comes in
> (aggregate_status_updates=0). While building a big Nagios box I came to the
> point where the service reaper thread was unable to reap fast enough to keep
> latency low. Changing it to 5 seconds updates made an incredible difference
> and now nagios hardly uses more than 10% CPU (I'd say 3-5 average). Startup
> time was also drastically reduced.
>
> While this box runs against Nagios 2.7 it's one of the configs I updated and
> used for testing Nagios 3.0 and it never complained about status updates
> aggregation.
>
> Right now that box runs 869 active checks per minutes with very light load
>
>
> Thomas
>
Nagios 3 requires that all status file updates are aggregated, at a
minimum 1 second interval. I'll update the docs to indicate this and
have Nagios log a warning if it sees the old aggregate_status_updates
variable in the config file.
Ethan Galstad,
Nagios Developer
---
Email: [email protected]
Website: http://www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]