[jira] [Commented] (CASSANDRA-7130) Make sstable checksum type configurable and optional

["Jason Brown (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14139595#comment-14139595 ] 

Jason Brown commented on CASSANDRA-7130:
----------------------------------------

I'm wondering if we really want to make it configurable: can we just pick one (probably xxhash) and go with it? While the code probably won't be that much, I wonder if we to push another choice onto users. That being said, it's probably trivial enough just to go ahead and knock it out - and it seems low-key enough to not have to wait for next-gen storage.

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