Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C37D18ADE for ; Wed, 13 Jan 2016 17:34:40 +0000 (UTC) Received: (qmail 75024 invoked by uid 500); 13 Jan 2016 17:34:40 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 75002 invoked by uid 500); 13 Jan 2016 17:34:40 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 74988 invoked by uid 99); 13 Jan 2016 17:34:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2016 17:34:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D0D022C1F5B for ; Wed, 13 Jan 2016 17:34:39 +0000 (UTC) Date: Wed, 13 Jan 2016 17:34:39 +0000 (UTC) From: "Jim Witschey (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-10995) Consider disabling sstable compression by default in 3.x MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-10995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15096640#comment-15096640 ] Jim Witschey commented on CASSANDRA-10995: ------------------------------------------ [~iamaleksey] Jake had a good suggestion for getting more compressible sstables out of {{cassandra-stress}}: decrease the size of the population from which to insert. I'm working on determining if data generated like that actually does compress more than stress's default randomly-generated data, but if it does, do you think that would that be a reasonable proxy for a normal dataset w.r.t. 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 > 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)