You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2015/02/24 01:33:13 UTC

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

     [ https://issues.apache.org/jira/browse/CASSANDRA-7130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-7130.
---------------------------------------
       Resolution: Duplicate
    Fix Version/s:     (was: 2.1.4)

resolving as duplicate then (even though it's not quite)

> 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
>            Assignee: Jason Brown
>            Priority: Minor
>              Labels: performance
>
> 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)