[CASSANDRA-8614] Select optimal CRC32 implementation at runtime

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Component/s: Legacy/Local Write-Read Paths, Local/Compaction
• Labels: performance
• Assignee: Ariel Weisberg
• Reporter: Ariel Weisberg

Authors

Ariel Weisberg

Reviewers

Benedict Elliott Smith

• Created: 13/Jan/15 21:23
• Updated: 16/Apr/19 09:31
• Resolved: 19/Feb/15 12:25

Description

JDK 8 has support for an intrinsic for CRC32 that runs at 12-13 gigabytes/sec per core in my quick and dirty test. PureJavaCRC32 is < 800 megabytes/sec if I recall and it has a lookup table that evicts random cache lines every time it runs.

In order to capture the benefit of that when it is available we can select a CRC32 implementation at startup in a static block.

If JDK 8 is not what is running we can fall back to the existing PureJavaCRC32 implementation.

Issue Links

• is depended upon by: CASSANDRA-8684 Replace usage of Adler32 with CRC32
• is related to: CASSANDRA-8836 Factor out CRC32Ex into a separate maven dependency