[jira] [Commented] (CASSANDRA-10735) Support netty openssl (netty-tcnative) for client encryption

["Andy Tolbert (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15191333#comment-15191333 ] 

Andy Tolbert commented on CASSANDRA-10735:
------------------------------------------

Had planned to return to doing some more benchmarking on this at some point, but time moves quickly!  Would be willing to help contribute to this in any way that would be helpful (testing/profiling/implementation/etc.), [my attempt|https://github.com/tolbertam/cassandra/commit/eaaed26ca84304f7839213f5b0c5534d50f02185] to get this working was a least effort stab at things just to see what the numbers look like.   There is also the cassandra-stress side of this as well which it looks like I didn't include, can provide that too if that is helpful.

> Support netty openssl (netty-tcnative) for client encryption
> ------------------------------------------------------------
>
>                 Key: CASSANDRA-10735
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10735
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Andy Tolbert
>            Assignee: Aleksey Yeschenko
>             Fix For: 3.x
>
>         Attachments: nettyssl-bench.tgz, nettysslbench.png, nettysslbench_small.png
>
>
> The java-driver recently added support for using netty openssl via [netty-tcnative|http://netty.io/wiki/forked-tomcat-native.html] in [JAVA-841|https://datastax-oss.atlassian.net/browse/JAVA-841], this shows a very measured improvement (numbers incoming on that ticket).   It seems likely that this can offer improvement if implemented C* side as well.
> Since netty-tcnative has platform specific requirements, this should not be made the default, but rather be an option that one can use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)