You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/11/19 05:35:03 UTC
[jira] [Updated] (CASSANDRA-10995) Consider disabling sstable
compression by default in 3.x
[ https://issues.apache.org/jira/browse/CASSANDRA-10995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
C. Scott Andreas updated CASSANDRA-10995:
-----------------------------------------
Component/s: Compression
> Consider disabling sstable compression by default in 3.x
> --------------------------------------------------------
>
> Key: CASSANDRA-10995
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10995
> Project: Cassandra
> Issue Type: Improvement
> Components: Compression
> Reporter: Aleksey Yeschenko
> Assignee: Jim Witschey
> Priority: Major
>
> With the new sstable format introduced in CASSANDRA-8099, it's very likely that enabled sstable compression is no longer the right default option.
> [~slebresne]'s [blog post|http://www.datastax.com/2015/12/storage-engine-30] on the new storage engine has some comparison numbers for 2.2/3.0, with and without compression that show that in many cases compression no longer has a significant effect on sstable sizes - all while sill consuming extra resources for both writes (compression) and reads (decompression).
> We should run a comprehensive set of benchmarks to determine whether or not compression should be switched to 'off' now in 3.x.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org