<tt>nagios-users-bounces@lists.sourceforge.net schrieb am 05.06.2008 11:57:32: > I'm running nagios 3.0.2 on a dell poweredge 2850 server with 2gb ram > and a xeon 2.80GHz cpu. > Also running on this server, ndo utils 1.47b, pnp, nagvis and > nagiosla.(os is newest rhel5) > Nagios checks 113 hosts and 660 services, most of them every 3 minutes. > Server load is over 1.3 most of the time due to the mysql database, I think. > Another problem is, I get frequently high ping times in the local > network the nagios server belongs to. > > What servers do you use for this count of checks. > Should I split it into two nagios servers? > > It would be nice to get some suggestions. I'm running nearly the same set, just missing nagiosla, on RHEL5.2.</tt> <tt>Machine is a HP DL360 Quad-Core E5405 @ 2.00GHz with 5GB Ram.</tt> <tt>Local 10k SAS hdd only, no SAN, local mysql.</tt> <tt>400 hosts, 1500 servicechecks.</tt> <tt>1400 servicechecks are scheduled every minute, 100 once per day.</tt> <tt>I do get roundabout 1100-1200 checks throughput each minute,</tt> <tt>averaging 80% of the expected checks each minute with a very</tt> <tt>good latency.</tt> <tt>Check Execution Time: 0.01 sec 10.02 sec 0.417 sec</tt> <tt>Check Latency: 0.00 sec 7.19 sec 1.623 sec </tt> <tt>I've done extensive performance tests and in summary the best</tt> <tt>practices to speed up things:</tt> <tt>- RAM, RAM, RAM. Both for mysql (see below) and for increased</tt> <tt> filesystem buffers.</tt> <tt>- Reserve enough memory for mysql to keep things buffered as</tt> <tt> long as possible:</tt> <tt> I'm currently using these settings:</tt> <tt> </tt> <tt> innodb_buffer_pool_size = 1024M</tt> <tt> innodb_additional_mem_pool_size = 64M</tt> <tt> innodb_log_file_size = 512M</tt> <tt> innodb_log_buffer_size = 64M</tt> <tt> innodb_flush_log_at_trx_commit = 1</tt> <tt> Beware: this will spike up mysql memory usage to nearly 2GB virtual</tt> <tt> and roundabout 1GB of resident memory.</tt> <tt>- use npcd for bulk processing performance data for pnp. Direct</tt> <tt> injections for each performance result will stall your checks</tt> <tt> and result in huge check latency</tt> <tt>- set "data_processing_options=4061953" in your ndomod.cfg</tt> <tt> By default ndo parses and injects every event from nagios,</tt> <tt> which results in unnecessary mysql queries and bloats the</tt> <tt> database over time - even more slowing down ndo since it</tt> <tt> automatically purges old data. With this option you won't have</tt> <tt> any aging data and the database only holds realtime info</tt> <tt> Attention: This setting is totally perfect with Nagvis, but I have</tt> <tt> no clue if nagiosla needs ndo and what information - so double check</tt> <tt> that.</tt> <tt>- I'm using "use_large_installation_tweaks=1" too, but I'm not sure</tt> <tt> if it would have any impact on your scenario.</tt> <tt>- I've manually built an SQL index over some tables for ndo, but I</tt> <tt> doubt it would have much impact on your scenario either.</tt> <tt>hth</tt> <tt>Regards</tt> <tt> Sascha</tt> -- Sascha Runschke Netzwerk- und Systemmanagement Telefon : +49 (201) 102-1879 Mobil : +49 (173) 5419665 Fax : +49 (201) 102-1102105 GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522