cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Eriksson (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-3127) Message (inter-node) compression
Date Fri, 25 May 2012 14:34:23 GMT

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

Marcus Eriksson edited comment on CASSANDRA-3127 at 5/25/12 2:32 PM:
---------------------------------------------------------------------

Could we perhaps always compress the message and check if the resulting message is smaller
than the original one? And then of course send the smallest one over the wire.

MySQL does that when using client->server compression for example.

I'll assign this to me and start poking around a bit
                
      was (Author: krummas):
    Could we perhaps always compress the message and check if the resulting message is smaller
than the original one?

MySQL does that when using client->server compression for example.

I'll assign this to me and start poking around a bit
                  
> Message (inter-node) compression
> --------------------------------
>
>                 Key: CASSANDRA-3127
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3127
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Sylvain Lebresne
>            Assignee: Marcus Eriksson
>            Priority: Minor
>
> CASSANDRA-3015 adds compression of streams. But it could be useful to also compress some
messages.
> Compressing messages is easy, but what may be little bit trickier is when and what messages
to compress to get the best performances.
> The simple solution would be to just have it either always on or always off. But for
very small messages (gossip?) that may be counter-productive. On the other side of the spectrum,
this is likely always a good choice to compress for say the exchange of merkle trees across
data-centers. We could maybe define a size of messages after which we start to compress. Maybe
the option to only compress for cross data-center messages would be useful too (but I may
also just be getting carried away). 

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

        

Mime
View raw message