[ https://issues.apache.org/jira/browse/CASSANDRA-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedict reopened CASSANDRA-7130: --------------------------------- Assignee: (was: Benedict) As discussed on CASSANDRA-7928, this is probably worth revisiting, especially as it isn't too difficult. Probably worth delaying until next-gen storage is out the gate though. > Make sstable checksum type configurable and optional > ---------------------------------------------------- > > Key: CASSANDRA-7130 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7130 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Benedict > Priority: Minor > Labels: performance > Fix For: 3.0 > > > A lot of our users are becoming bottlenecked on CPU rather than IO, and > whilst Adler32 is faster than CRC, it isn't anything like as fast as xxhash > (used by LZ4), which can push Gb/s. I propose making the checksum type > configurable so that users who want speed can shift to xxhash, and those who > want security can use Adler or CRC. > It's worth noting that at some point in the future (JDK8?) optimised > implementations using latest intel crc instructions will be added, though > it's not clear from the mailing list discussion if/when that will materialise: > http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2013-May/010775.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)