[jira] [Comment Edited] (CASSANDRA-5862) Switch to adler checksum for sstables

["T Jake Luciani (JIRA)" <ji...@apache.org>]

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

T Jake Luciani edited comment on CASSANDRA-5862 at 8/8/13 8:45 PM:
-------------------------------------------------------------------

bq. the dual checksum fields in CRAR are a bit clunky; the approach of instantiating the correct one in the constructor that you use in CIS is cleaner.

My concern was the instance would be re-used across multiple sstables therefore should be chosen per buffer. Is that not the case?
                
      was (Author: tjake):
    .bq the dual checksum fields in CRAR are a bit clunky; the approach of instantiating the correct one in the constructor that you use in CIS is cleaner.

My concern was the instance would be re-used across multiple sstables therefore should be chosen per buffer. Is that not the case?
                  
> 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