Hi Praveen,
You can try the implemented solution with the latest snapshot release
from:
https://oosnmp.net/dist/snapshot/org/snmp4j/snmp4j/2.2.2-SNAPSHOT/snmp4j-2.2.2-20130604.002021-21.jar
A backport to the 1.x will be technically possible and available next
week, if no problems with this fix appear during further testing.
Best regards,
Frank
Am 03.06.2013 14:54, schrieb Praveen Jain:
Hi Frank,
Thanks a lot for quick reply. I would really appreciate if you backport the
fix into 1.x branch. Please let me know if there is a place where I can
track that (any issue tracking system). In case the backporting idea is
dropped for 1.x branch, please provide a patch so that I can apply the same
on source code. Thanks.
Regards,
Praveen.
-----Original Message-----
From: snmp4j-boun...@agentpp.org [mailto:snmp4j-boun...@agentpp.org] On
Behalf Of Frank Fock
Sent: Monday, June 03, 2013 2:59 AM
To: snmp4j@agentpp.org
Subject: Re: [SNMP4J] Performance hotspot in Cipher.getInstance() method
call
Hi Praveen,
SNMP4J is not caching the cipher object. Apparently, the performance
overhead of retrieving a Cipher instance is not that great with newer Java
versions.
Nevertheless, I am currently working on a caching solution, which does not
introduce a new bootleneek for multi-threaded usage for SNMP4J 2.x.
If it will possible, I will also provide a backport to the 1.x branch.
Best regards,
Frank
Am 30.05.2013 13:03, schrieb Praveen Jain:
We are using SNMP4J version 1.11.4 for a legacy application running in
Java
1.4 environment. The application behaved slower than expected and
profiling showed that there is hotspot in PrivDES.encrypt() method.
This method in turn calls javax.crypto.Cipher.getInstance(String)
method (apparently on each message transmission) and
Cipher.getInstance(String) is the expensive and CPU intensive call. Can
you please suggest if:
1. This might be due wrong way of calling SNMP4J api (and also point
to a reference code for correct usage to prevent this problem)
2. Is this an inherent problem with Java 1.4 code?
3. Is this a problem with SNMP 1.11.4 code (it is not caching the
obtained cipher object)?
Thanks in advance for the help.
-Praveen
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j
--
---
AGENT++
Maximilian-Kolbe-Str. 10
73257 Koengen, Germany
https://agentpp.com
Phone: +49 7024 8688230
Fax: +49 7024 8688231
_______________________________________________
SNMP4J mailing list
SNMP4J@agentpp.org
http://lists.agentpp.org/mailman/listinfo/snmp4j
