Very interesting. I don't understand french a lot.... are there the steps to follow for the optimization ?
Regards Marco -----Messaggio originale----- Da: Alexandre Bray [mailto:in...@opendoc.net] Inviato: sabato 7 aprile 2012 18:50 A: Nagios Users List Oggetto: Re: [Nagios-users] use_large_installation_tweaks hello, Here are some tests with the option use_large_installation_tweaks. There are no graphics for the memory but the CPU load and scheduling. If this little help you ... http://www.opendoc.net/solutions/comment-ameliorer-performances-nagios Alexandre On 04/04/2012 17:18, C. Bensend wrote: > >> Does anyone has configured it ? >> >> Is it really a good way to follow to reduce memory usage ? > > For me, it was a good way to reduce memory and CPU, and it helped with > check latencies. > > Although, the absolute best way to reduce check latencies for me has > been to dump NDOUtils. Good lord, that was awful, had to restart > Nagios three times a week. > > Benny > > ---------------------------------------------------------------------------- -- For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ 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 ------------------------------------------------------------------------------ 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@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