cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Tolbert (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10735) Support netty openssl (netty-tcnative) for client encryption
Date Wed, 25 Nov 2015 02:10:11 GMT


Andy Tolbert commented on CASSANDRA-10735:

One thing I need to confirm is why the orange config and blue configs, which both used OpenSSL
on the C* side, show a difference in gc'd mb.  It could be that the TLS version or cipher
negotiated may have been different between using jdk ssl and openssl in the driver.  I've
seen in the past that I can get better throughput with 1.1 vs 1.2.  I'll do a packet trace
soon to confirm everything in consistent between the configurations.

> Support netty openssl (netty-tcnative) for client encryption
> ------------------------------------------------------------
>                 Key: CASSANDRA-10735
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Andy Tolbert
>             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|]
in [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

View raw message