[SNMP4J] Frank - Need help Urgent!!!!!!

ignacio.izaga at hp.com ignacio.izaga at hp.com
Mon Jan 9 21:55:19 CET 2006


Hello Frank,

I am currently involved in the project with Eva (but working on a
different component) and I can provide some information.

I am not sure how Eva is destroying the threads. However, I know why she
might not be using the GETBULK request.

Eva mentioned that performance is a high priority requirement in the
application. My understanding is that the GETBULK mechanism is performing
a GETNEXT iteration. The time it would take to perform "22 getnext" would
be 22(RTT + Tp) where RTT is the round-trip time and Tp is the Time it
takes the SNMP agent in the printer to process each the snmp request.

If the RTT is similar to the Tp, then it makes sense to perform 22
GETNEXT. However, if the RTT is >> than the Tp, it makes sense to create
22 threads and send each thread after a certain delay (usually Tp). The
time it would take to perform the 22 requests in this case would be RTT +
22*Tp. This is why I think Eva is working with the 22 threads approach.

Do you see a faster way to perform the 22 requests? In addition, why is
Java 1.4 behaving different than 1.5? I have tested the application by my
self and it is quite easy to hang the sw on 1.4 but not on 1.5.

Thanks again,

Ignacio







More information about the SNMP4J mailing list