[
https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-1722:
--------------------------------
Hmm, the biggest chunk of CPU (by far) according to jmc is spent in
{{com.sun.crypto.provider.AESCrypt.decryptBlock()}} (30%) and
{{com.sun.crypto.provider.AESCrypt.encryptBlock()}} (26%). A total of over 64% is spent in
the {{com.sun.crypto.provider}} package !
I'll try to improve other things, but I won't be able to do much about this.
Pinging [~NadirX] to take a look; perhaps a different encryption algorithm (or a smaller
key size) will help, but I doubt it. Looks like encryption does have a price tage to
it...
One thing I'll investigate is whether encryption is done sequentially, using the same
cipher, or whether we can parallelize this. If we can, then even a costly encryption /
decryption alg won't have much impact.
Improve performance of ENCRYPT protocol
---------------------------------------
Key: JGRP-1722
URL:
https://issues.jboss.org/browse/JGRP-1722
Project: JGroups
Issue Type: Enhancement
Affects Versions: 3.4
Reporter: Martin Gencur
Assignee: Bela Ban
Fix For: 3.5
A stress tests with the following setup showed that performance (reads and writes/sec) is
halved when ENCRYPT protocol is enabled:
Infinispan had distributed sync cache with 2 owners on 4 nodes, no transactions. The
stress test used 10 threads on each node accessing 1024 byte entries, no conflicts on
keys, 20 % writes, 80 % reads.
It would be great if we could improve the performance of ENCRYPT protocol.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira