cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-10995) Consider disabling sstable compression by default in 3.x
Date Mon, 11 Jan 2016 22:48:40 GMT

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

Joshua McKenzie commented on CASSANDRA-10995:
---------------------------------------------

(You're going to love me for this): We need to make sure we benchmark this on Windows as well,
since the mmap performance on the platform vs. buffered has historically had a larger disparity
than on linux. That being said, uncompressed was always considerably faster when tested on
Windows but we do want to make sure we cover that platform.

> 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
>            Reporter: Aleksey Yeschenko
>            Assignee: Jim Witschey
>
> 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
(v6.3.4#6332)

Mime
View raw message