cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "C. Scott Andreas (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-10995) Consider disabling sstable compression by default in 3.x
Date Mon, 19 Nov 2018 05:35:03 GMT


C. Scott Andreas updated CASSANDRA-10995:
    Component/s: Compression

> Consider disabling sstable compression by default in 3.x
> --------------------------------------------------------
>                 Key: CASSANDRA-10995
>                 URL:
>             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|] 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message