You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ariel Weisberg (JIRA)" <ji...@apache.org> on 2014/12/10 18:06:13 UTC

[jira] [Commented] (CASSANDRA-4139) Add varint encoding to Messaging service

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

Ariel Weisberg commented on CASSANDRA-4139:
-------------------------------------------

I think variable length integer encoding could be a big space saving in several contexts, but there is an argument against varints.

If you want to do zero deserialization/copy varints will fight you because you can't random access fields by offset. 

What you can do instead is use generic compression. Counter-intuitive but think of the two use cases. I care about bandwidth therefore I need compression anyways for non-integer fields, or I don't care about bandwidth so why not maximize performance.

Where this becomes important is in handling large messages where you don't want parse all of it because you are forwarding or may not consume the entire contents. If you have varints and want to be lazy it gets tricky.

I am up for trying it and out and measuring..

> Add varint encoding to Messaging service
> ----------------------------------------
>
>                 Key: CASSANDRA-4139
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4139
>             Project: Cassandra
>          Issue Type: Sub-task
>          Components: Core
>            Reporter: Vijay
>            Assignee: Ariel Weisberg
>             Fix For: 3.0
>
>         Attachments: 0001-CASSANDRA-4139-v1.patch, 0001-CASSANDRA-4139-v2.patch, 0001-CASSANDRA-4139-v4.patch, 0002-add-bytes-written-metric.patch, 4139-Test.rtf, ASF.LICENSE.NOT.GRANTED--0001-CASSANDRA-4139-v3.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)