cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-7130) Make sstable checksum type configurable and optional
Date Thu, 18 Sep 2014 23:59:34 GMT

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

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

Thinking about it, and since I was bit by this today (or, at least, complaining about it internally),
I'll take a stab at this. Would anybody mind if I did this work on 2.1?

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

Mime
View raw message