You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Charles Connell (Jira)" <ji...@apache.org> on 2023/06/09 13:41:00 UTC
[jira] [Commented] (HBASE-27907) [hbase-thirdparty] Include netty-tcnative in hbase-shaded-netty
[ https://issues.apache.org/jira/browse/HBASE-27907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730958#comment-17730958 ]
Charles Connell commented on HBASE-27907:
-----------------------------------------
After further examination, I found problems with my testing setup that led to an incorrect conclusion. I now believe netty-tcnative is not advantageous.
> [hbase-thirdparty] Include netty-tcnative in hbase-shaded-netty
> ---------------------------------------------------------------
>
> Key: HBASE-27907
> URL: https://issues.apache.org/jira/browse/HBASE-27907
> Project: HBase
> Issue Type: Improvement
> Components: thirdparty
> Reporter: Charles Connell
> Assignee: Charles Connell
> Priority: Minor
>
> At my company, HubSpot, we are starting to use HBase's TLS support in our clusters. I've done some experiments with different TLS implementations to see which has the best performance.
> I have tested Java 11 without {{{}UseAESCTRInstrinics{}}}, Java 11 with {{{}UseAESCTRInstrinsics{}}}, with and without {{netty-tcnative}} installed, on both {{x86_64}} and {{{}arm64{}}}. I will attach some charts.
> -I have found that using the {{netty-tcnative}} library gives the best performance overall, and I would like to see it included in HBase by default.-
> This ticket is for tracking the change to hbase-thirdparty and producing a new version of that. Another ticket will track the inclusion of that new version in HBase, which requires a few code changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)