> On Fri, 29 Oct 2004 15:37:10 -0500 (CDT) Joe wrote:
> JC> >         time snmpwalk -c public -v 2c localhost ifIndex
> JC> >         time snmpgetnext -c public -v 2c localhost ifTable.2
> JC> 
> JC> Nope...both of those commands took about the same length of time (0.22s &
> JC> 0.29s).
> 
> Interesting.. so which column is taking so long? Try this:
> 
>       time snmpwalk -c public -v 2c localhost ifEntry.1
>       time snmpwalk -c public -v 2c localhost ifEntry.2
>       ...
>       time snmpwalk -c public -v 2c localhost ifEntry.22
> 
> And see who the culprit is..

Well, interestingly, my times for the 22 columns (in order) are:
0.071472, 0.124233, 0.172033, 0.176264, 0.165005, 0.176065, 0.206678, 0.185556
0.087073, 0.158067, 0.195877, 0.062297, 0.101777, 0.172579, 0.050624, 0.163356
0.172058, 0.020449, 0.122631, 0.092182, 0.102396, 0.242120

So it seems that there isn't one column that is especially bad, but add those
numbers up and it becomes appx 3 seconds.

Note that those numbers are from the -Ct option.  time gave numbers similar but
a little higher.
- Joe




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to