how to fix excessive latency

[wwanghongrui]

Hi,guys~

Our nagios server envrionment: Nagios3.2.0 + Suse10-sp2 x86_64 + 8 GB mem + 4 x ( Xeon(R) CPU  E7420  @ 2.13GHz )
We have 500+ active check hosts and 3k+ active check services.  I have adjust some perfomance parameters in nagios.cfg, like below:
use_large_installation_tweaks=1
child_processes_fork_twice=0
enable_environment_macros=0
check_result_reaper_frequency=5
max_check_result_reaper_time=30

But, The nagios performance is still bad, like below:

Services Actively Checked:Time FrameServices Checked
<= 1 minute:271 (9.4%)
<= 5 minutes:1749 (60.4%)
<= 15 minutes:2824 (97.4%)
<= 1 hour:2898 (100.0%)
Since program start:  2869 (99.0%)

MetricMin.Max.Average
Check Execution Time:  0.09 sec32.23 sec1.113 sec
Check Latency:1.12 sec212.59 sec116.329 sec
Percent State Change:0.00%23.88%0.05%


Hosts Acrively Checked:Time FrameHosts Checked
<= 1 minute:32 (5.5%)
<= 5 minutes:419 (71.5%)
<= 15 minutes:586 (100.0%)
<= 1 hour:586 (100.0%)
Since program start:  586 (100.0%)

MetricMin.Max.Average
Check Execution Time:  0.08 sec4.29 sec3.035 sec
Check Latency:0.00 sec135.25 sec116.420 sec
Percent State Change:0.00%11.32%0.09%




 How could I find which services check or hosts check cause this seriously check latency? 


Regards 

HongRui Wang
mail: wwanghongrui at cebbank.com
2010-06-28
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100628/a91bdf5a/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
-------------- next part --------------
_______________________________________________
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