cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Sanders (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5862) Switch to adler checksum for sstables
Date Tue, 24 Sep 2013 06:43:05 GMT

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

Bert Sanders commented on CASSANDRA-5862:
-----------------------------------------

Thanks, my bad, I was confused.

If my understanding is correct, SStables are a set of 2 files, 
one index, with bloom filters and Key/offset pairs
and one for data by column.

So I guess this issue is only about checksumming of the data part.

And about real-world benefits : 
I guess that if testing with Adler32 was enough to measure benefits, 
a faster Hash should be even easier to measure.

                
> Switch to adler checksum for sstables
> -------------------------------------
>
>                 Key: CASSANDRA-5862
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5862
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: T Jake Luciani
>             Fix For: 2.0.1
>
>         Attachments: 5862.txt
>
>
> Adler is significantly faster than CRC32: http://java-performance.info/java-crc32-and-adler32/
> (Adler is weaker for short inputs, so we should leave the commitlog alone, as it checksums
each mutation individually.)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message