Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 11 Dec 2011 22:02:40 +0000 (UTC)
From: "Jonathan Ellis (Issue Comment Edited) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1996875313.63061.1323640960176.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1691424904.62751.1323623079907.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Issue Comment Edited] (CASSANDRA-3611) Make checksum on a
 compressed blocks optional
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis edited comment on CASSANDRA-3611 at 12/11/11 10:02 PM:
----------------------------------------------------------------------

My gut reaction is there's got to be some kind of Doing It Wrong if checksum-on-uncompress isn't virtually free.  (Related: CASSANDRA-3610.)
                
      was (Author: jbellis):
    My gut reaction is there's got to be some kind of Doing It Wrong if checksum-on-uncompress isn't virtually free.  (Related: CASSANDRA-3160.)
                  
> Make checksum on a compressed blocks optional
> ---------------------------------------------
>
>                 Key: CASSANDRA-3611
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3611
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1
>            Reporter: Vijay
>            Assignee: Vijay
>            Priority: Minor
>             Fix For: 1.1
>
>
> Currently every uncompressed block is run against checksum algo, there is cpu overhead in doing same... We might want to make it configurable/optional for some use cases which might not require checksum all the time.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira