[
https://issues.apache.org/jira/browse/CASSANDRA-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13288712#comment-13288712
]
Jonathan Ellis commented on CASSANDRA-3127:
-------------------------------------------
Yes, I'd like to see LZF vs Snappy if possible. Otherwise this looks
reasonable. One change to make is that we're introducing just one
MessagingService version change per major release, so sticking with VERSION_12
here is fine.
> 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
> Fix For: 1.2
>
> Attachments:
> 0001-CASSANDRA-3127-compress-messages-between-nodes.patch,
> CASSANDRA-3127.patch, CHECK_SIZES-CASSANDRA-3127.patch
>
>
> 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
