Any upcoming release?

[Andreas Ericsson]

On 04/05/2012 07:31 AM, Yu Watanabe wrote:
> Hi all!
> 
> I would like to know if there are any plans for the nagios v 3.4.x.
> It has been a while since the last release so I was very curious about it.
> 
> It would helpful if the nagios team can share the information.
> 

There is. Nagios 3.4 will be a single-threaded and event-driven application
that sports an I/O-broker and vastly improved check performance. In essence,
we've removed 2 fork() calls, 4 disk searches, 2 filewrites and 2 filereads
from each check being performed. There's also a fixed usage of the current
scheduling queue implementation which turns scheduling new checks from its
current O(n) behaviour to O(1). This will provide a huge benefit for large
installations, and combined with the worker process code we're currently
seeing a 12-fold increase in the amount of checks Nagios can execute, but
it's still too early to tell what other things are affected. The external
command pipe might be a bottleneck if one uses large amounts of passive
checks, for example.

It's currently in late alpha, so beta releases should be available in a
month or so.

-- 
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.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
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