[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=12824547#comment-12824547 ] 

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

I think this is only true if (a) there is no communication between joiner and coordinator needed or (b) the transport is reliable.
* (a) If we have a shared keystore or username/password encryption, then this works
* (b) If we need to send a key request to the coord, and the coord sends a response, then either the transport needs to be reliable or UNICAST needs to be below ENCRYPT, or else these requests are sent *unreliably* and might get lost. A possible solution for (b) could be to assume that the message sending is unreliable and send the key request to the coordinator until a valid key is received. In this case, ENCRYPT could be moved under NAKACK/UNICAST.

[~mgencur] Either you used TCP as transport, or you were just lucky that the message wasn't dropped. Under real stress, there are no guarantees that a message isn't dropped.
                
> 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