[CASSANDRA-16360] CRC32 is inefficient on x86

• Type: Improvement
• Status: Patch Available
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 5.x
• Component/s: Messaging/Client, Messaging/Internode
• Labels: protocolv6
• Change Category: Semantic
• Complexity: Challenging
• Platform: All

Test and Documentation Plan

Run CI, the native protocol specification will need to be updated afterwards.

• Assignee: Maxim Muzafarov
• Reporter: Avi Kivity

Authors

Maxim Muzafarov

• Created: 17/Dec/20 10:19
• Updated: 20/Oct/23 13:00

Description

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).

Issue Links

• is related to: CASSANDRA-18780 ConnectionBurnTest fails with NullPointerException
• is related to: CASSANDRA-13908 Add JDK9 new CRC32C checksum
• is related to: HADOOP-15033 Use java.util.zip.CRC32C for Java 9 and above
• is related to: CASSANDRA-16645 Add a microbenchmark for checksum calculation
• links to: GitHub Pull Request #2647
• links to: HARDWARE INSTRUCTION BASED CRC32C