[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: [DISCUSS] Using ACCP or tc-native by default
From:       "German Eichberger via dev" <dev () cassandra ! apache ! org>
Date:       2023-06-23 20:43:06
Message-ID: MN0PR21MB3074E8A74AE83ECFDF9F671DFF23A () MN0PR21MB3074 ! namprd21 ! prod ! outlook ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

+1 to ACCP - we love performance.
________________________________
From: David Capwell <dcapwell@apple.com>
Sent: Thursday, June 22, 2023 4:21 PM
To: dev <dev@cassandra.apache.org>
Subject: [EXTERNAL] Re: [DISCUSS] Using ACCP or tc-native by default

+1 to ACCP

On Jun 22, 2023, at 3:05 PM, C. Scott Andreas <scott@paradoxica.net> wrote:

+1 for ACCP and can attest to its results. ACCP also optimizes for a range of hash \
functions and other cryptographic primitives beyond TLS acceleration for Netty.

On Jun 22, 2023, at 2:07 PM, Jeff Jirsa <jjirsa@gmail.com> wrote:


Either would be better than today.

On Thu, Jun 22, 2023 at 1:57 PM Jordan West \
<jwest@apache.org<mailto:jwest@apache.org>> wrote: Hi,

I'm wondering if there is appetite to change the default SSL provider for Cassandra \
going forward to either ACCP [1] or tc-native in Netty? Our deployment as well as \
others I'm aware of make this change in their fork and it can lead to significant \
performance improvement. When recently qualifying 4.1 without using ACCP (by \
accident) we noticed p99 latencies were 2x higher than 3.0 w/ ACCP. Wiring up ACCP \
can be a bit of a pain and also requires some amount of customization. I think it \
could be great for the wider community to adopt it.

The biggest hurdle I foresee is licensing but ACCP is Apache 2.0 licensed. Anything \
else I am missing before opening a JIRA and submitting a patch?

Jordan


[1]
https://github.com/corretto/amazon-corretto-crypto-provider


[Attachment #3 (text/html)]

<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} \
</style> </head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 11pt; \
color: rgb(0, 0, 0);" class="elementToProof"> +1 to ACCP - we love performance.</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" \
style="font-size:11pt" color="#000000"><b>From:</b> David Capwell \
&lt;dcapwell@apple.com&gt;<br> <b>Sent:</b> Thursday, June 22, 2023 4:21 PM<br>
<b>To:</b> dev &lt;dev@cassandra.apache.org&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: [DISCUSS] Using ACCP or tc-native by default</font>
<div>&nbsp;</div>
</div>
<div style="line-break:after-white-space">+1 to ACCP<br>
<div><br>
<blockquote type="cite">
<div>On Jun 22, 2023, at 3:05 PM, C. Scott Andreas &lt;scott@paradoxica.net&gt; \
wrote:</div> <br class="x_Apple-interchange-newline">
<div>
<div>
<div>
<div>+1 for ACCP and can attest to its results. ACCP also optimizes for a range of \
hash functions and other cryptographic primitives beyond TLS acceleration for \
Netty.<br> </div>
<div><br>
</div>
<blockquote type="cite">
<div>On Jun 22, 2023, at 2:07 PM, Jeff Jirsa &lt;jjirsa@gmail.com&gt; wrote:<br>
</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div dir="ltr">Either would be better than today.&nbsp;<br>
</div>
<div><br>
</div>
<div class="x_gmail_quote">
<div class="x_gmail_attr" dir="ltr">On Thu, Jun 22, 2023 at 1:57 PM Jordan West \
&lt;<a href="mailto:jwest@apache.org">jwest@apache.org</a>&gt; wrote:<br> </div>
<blockquote class="x_gmail_quote" style="margin:0px 0px 0px 0.8ex; border-left:1px \
solid rgb(204,204,204); padding-left:1ex"> <div>Hi,<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I'm wondering if there is appetite to change the default SSL provider \
for Cassandra going forward to either ACCP [1] or tc-native in Netty? Our deployment \
as well as others I'm aware of make this change in their fork and it can lead to \
significant  performance improvement. When recently qualifying 4.1 without using ACCP \
(by accident) we noticed p99 latencies were 2x higher than 3.0 w/ ACCP. Wiring up \
ACCP can be a bit of a pain and also requires some amount of customization. I think \
it could be great  for the wider community to adopt it.&nbsp;<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">The biggest hurdle I foresee is licensing but ACCP is Apache 2.0 \
licensed. Anything else I am missing before opening a JIRA and submitting a \
patch?<br> </div>
<div dir="auto"><br>
</div>
<div dir="auto">Jordan&nbsp;<br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div>[1]&nbsp;<br>
</div>
<div><a rel="noopener noreferrer" \
href="https://github.com/corretto/amazon-corretto-crypto-provider" \
originalsrc="https://github.com/corretto/amazon-corretto-crypto-provider" \
shash="wutlTZz8QRBnmEd2OrfAP4ma9cH6wII3Y4GqXMgmRu5ffD100lfkvLVM+wu8D7C69G4DnXhqRvekU92 \
vJA8rk1hvmFxCHoFhB8Iup8fslfclP1rG+O9r3Thy0INCiARG4oSbLFMpyGU/9CbrwCzWuOymGU9vHcILmlolfIhfTHM=">https://github.com/corretto/amazon-corretto-crypto-provider</a><br>
 </div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic