Im running 3 copies of the snmpd that is distributed with scotty (each
with a different port and different version of snmp, v1, v2c, v2u). This
machine is a Sun Ultra 2 with very little load and 64 megs of memory. The
manager is a Pentium Pro 180 with 64 megs of ram and very low load.
The script I am using to test makes use of the 'time' in Tcl (7.6). I
sequentially time 1 iteration, 2, 3, 4...10 iterations of simply opening a
session, getting the sysUpTime, and closing the session. When I do this,
I get about 330,000 microseconds for an SNMPv1 connection. With SNMPv2u,
I get about 370,000 microseconds, but for an SNMPv2c connection, I get
less than 2000. When I do this with two iterations, all the versions fall
back down to less than 2000 and approach a 'stable' about of time.
I expect there to be some overhead with opening and closing sessions, and
I do observe a curve in the plotted data indicating an initial startup
cost (Im assuming this is some sort of caching on the agent side), but NOT
with v2c. Im wondering if this is Tcl acting funny or if there are
significant differences between the v1, v2u and v2c code. Can anyone
explain what is going on here (or at least suggest if it is the manager or
agent that is creating the lag)?
If anyone would like to see data or code, let me know, I would be happy to
pass it along. Oh, BTW, this doesnt happen if I leave the connection open
and time the GETs I do of sysUpTime.
Thanks!
-Steve
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.