[
https://issues.apache.org/jira/browse/CASSANDRA-16360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751158#comment-17751158
]
Maxim Muzafarov commented on CASSANDRA-16360:
---------------------------------------------
[~samt], [~benedict] Since we've finished with the CASSANDRA-18255 and dropped
the jdk8 support, so I think there is nothing stopping us from continuing to
work on this issue, right?
It has been quite a while since the last message, so I wonder if there are any
new details that have come up since the last message. If so, please, share. I
have perused the above discussion and Alexei's plan and it makes sense to me to
proceed with preparing the patch.
> CRC32 is inefficient on x86
> ---------------------------
>
> Key: CASSANDRA-16360
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16360
> Project: Cassandra
> Issue Type: Improvement
> Components: Messaging/Client
> Reporter: Avi Kivity
> Priority: Normal
> Labels: protocolv6
> Fix For: 5.x
>
>
> The client/server protocol specifies CRC24 and CRC32 as the checksum
> algorithm (cql_protocol_V5_framing.asc). Those however are expensive to
> compute; this affects both the client and the server.
>
> A better checksum algorithm is CRC32C, which has hardware support on x86 (as
> well as other modern architectures).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
