Return-Path: 
 <user-return-29971-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6CA21D86C
	for <apmail-cassandra-user-archive@www.apache.org>;
 Thu,  8 Nov 2012 19:21:12 +0000 (UTC)
Received: (qmail 12735 invoked by uid 500); 8 Nov 2012 19:21:08 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 12707 invoked by uid 500); 8 Nov 2012 19:21:08 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 12698 invoked by uid 99); 8 Nov 2012 19:21:08 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 19:21:08 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of btoddb@gmail.com designates
 209.85.219.44 as permitted sender)
Received: from [209.85.219.44] (HELO mail-oa0-f44.google.com) (209.85.219.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 19:21:02 +0000
Received: by mail-oa0-f44.google.com with SMTP id n5so3482485oag.31
        for <user@cassandra.apache.org>; Thu, 08 Nov 2012 11:20:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=p8fQopMkw5a7s7WFk2mDo5jUuoeeE+xAcNQYXMM+1Yc=;
        b=zpa5oBb9lka2t+KqCWz/qKwgz95Urkr75S8Wdu76p+z7+YL+aewc1SJxmPiQ0/t/45
         RBeL/GE/G3FqgZo06sUprgn/4vPYIQ7K37A6LIo+W+wxzFbGsAFbpdDJutcuTD/ngRhn
         u5J74scFIdoMUCDLdGJug+BQoUNDItxqw1bICMZ2iiuxBHg9H2OVd0H0gRvmQRq7rrIm
         Z6gdbcFOxXpXEVXb/N/KupGyY/N5A44kWSz1dp8iZPhfTYc+uI/DsusuWrhB1/jSD4I8
         bqx+uJqTEhfub28wYrO9jIgSBbiXmIRInXjMUefq1YmwrJAQXZr8z3qMLIC37/mP+j7w
         g5Pg==
MIME-Version: 1.0
Received: by 10.60.27.36 with SMTP id q4mr6013008oeg.111.1352402441018; Thu,
 08 Nov 2012 11:20:41 -0800 (PST)
Received: by 10.182.171.8 with HTTP; Thu, 8 Nov 2012 11:20:40 -0800 (PST)
In-Reply-To: <509BF726.8060309@filez.com>
References: 
 <CAH0yS3JA4auTH_e6BSS4OuOk4bhTV8=sR=Dg3F3fm7NL_4MMqA@mail.gmail.com>
	<509BF726.8060309@filez.com>
Date: Thu, 8 Nov 2012 11:20:40 -0800
Message-ID: 
 <CAH0yS3+cKC32JrvBqrXQb7uaEaHFS1MJaigCRVphK1uKWvLN1Q@mail.gmail.com>
Subject: Re: leveled compaction and tombstoned data
From: "B. Todd Burruss" <btoddb@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Checked: Checked by ClamAV on apache.org

we are running Datastax enterprise and cannot patch it.  how bad is
"kill performance"?  if it is so bad, why is it an option?


On Thu, Nov 8, 2012 at 10:17 AM, Radim Kolar <hsn@filez.com> wrote:
> Dne 8.11.2012 19:12, B. Todd Burruss napsal(a):
>
>> my question is would leveled compaction help to get rid of the tombstoned
>> data faster than size tiered, and therefore reduce the disk space usage?
>>
> leveled compaction will kill your performance. get patch from jira for
> maximum sstable size per CF and force cassandra to make smaller tables, they
> expire faster.
>