It's also good to note that only the Data files are compressed already.
Depending on your data the Index and other files may be a significant
percent of total on disk data.
On 05/02/2014 01:14 PM, tommaso barbugli wrote:
In my tests compressing with lzop sstables (with cassandra compression
turned on) resulted in approx. 50% smaller files.
Thats probably because the chunks of data compressed by lzop are way bigger
than the average size of writes performed on Cassandra (not sure how data
is compressed but I guess it is done per single cell so unless one stores)
2014-05-02 19:01 GMT+02:00 Robert Coli <rc...@eventbrite.com>:
On Fri, May 2, 2014 at 2:07 AM, tommaso barbugli <tbarbu...@gmail.com>wrote:
If you are thinking about using Amazon S3 storage I wrote a tool that
performs snapshots and backups on multiple nodes.
Backups are stored compressed on S3.
https://github.com/tbarbugli/cassandra_snapshotter
https://github.com/JeremyGrosser/tablesnap
SSTables in Cassandra are compressed by default, if you are re-compressing
them you may just be wasting CPU.. :)
=Rob