[jboss-jira] [JBoss JIRA] (JGRP-1722) Improve performance of ENCRYPT protocol

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12951228#comment-12951228 ] 

Bela Ban commented on JGRP-1722:
--------------------------------

Somewhat disappointing, but it looks as if the perf of ENCRYPT is largely a function of the speed of encryption and decryption. Adding a cipher pool didn't really improve performance for regular messages, but should improve it for {{OOB | DONT_BUNDLE}} messages.
Parallelization (e.g. concurrent decryption of all messages of a message batch) didn't help, either. The reason is that introducing yet another thread pool probably cancelled out the gains made, through increased context switching. I'll revisit this when baselining JGroups on JDK 7 where a shared fork-join thread pool can be used.
Also, uisng the asynchronous invocation API of JGroups would help as the encryption of the response would not have to be done on the same thread as the request, speeding of processing of message batches.
I'm resolving this for now, but I'm having a chat with Tristan to see if we can use a faster cipher...
                
> 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