> From: bheemesh v [mailto:bheem...@gmail.com]
> Sent: Friday, December 11, 2009 2:20 AM
> Attaching call graph of the profiled snmpd daemon.
> Find the graph in attachment.
I think you are misreading this chart. It does show that 81% of
runtime is spent inside run_alarms, but 0% of that time is spent on the routine
itself. You need to go way down and see that the ifTable and ipAddressTable
are using up most of the processing time, which is spent, for the most part,
sorting and comparing: array_qsort uses 14% of the time,
netsnmp_compare_netsnmp_index 27%, snmp_oid_compare 26%, etc. Nothing
surprising here - basically it's. What percentage of your total CPU timeis
this using? Perhaps lowering the rate of updates can trim the usage a bit, but
I don't know how to do that.
HTH,
Mike
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
