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

Marcus Eriksson commented on CASSANDRA-3127:
--------------------------------------------

I captured 75M of real traffic in one of our clusters and ran a few benchmarks
Both Snappy and LZF compressed to ~58M (LZF gave 0.2% better compression)
Snappy did the roundtrip (compress -> uncompress) in ~790ms for the 75M file
LZF did it in ~1170ms

Patch attached changes to Snappy, i did not see any of the issues xedin 
mentioned in CASSANDRA-3015, also removes VERSION_13
                
> 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

        

Reply via email to