Return-Path: 
 <user-return-27304-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 E0D31D572
	for <apmail-cassandra-user-archive@www.apache.org>;
 Sun,  1 Jul 2012 11:40:35 +0000 (UTC)
Received: (qmail 57605 invoked by uid 500); 1 Jul 2012 11:40:32 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 57388 invoked by uid 500); 1 Jul 2012 11:40:30 -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 57365 invoked by uid 99); 1 Jul 2012 11:40:30 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Jul 2012 11:40:30 +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 (athena.apache.org: domain of jwijgerd@gmail.com designates
 209.85.212.170 as permitted sender)
Received: from [209.85.212.170] (HELO mail-wi0-f170.google.com)
 (209.85.212.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Jul 2012 11:40:24 +0000
Received: by wibhq12 with SMTP id hq12so2037551wib.1
        for <multiple recipients>; Sun, 01 Jul 2012 04:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=references:in-reply-to:mime-version:content-transfer-encoding
         :content-type:message-id:cc:x-mailer:from:subject:date:to;
        bh=0nHkPwRizrGJhixufaEtel9nhjEmNKZA2RMXm2WV+XA=;
        b=pGu+WKnTAOx/VZDgBJBqmrXcgBdp5R6iGNI+jFTWiCnksK8/b31dPop8CAd1KnmUiT
         5LWe4DspaZ16w8Gt6/t1oQd9S0QVpcoR3hNuW5JyqVQZypf8Fl2crXvdW4dJqDMtuIf2
         uM0uPOCsilUtBNz5iT1Cu1GZ6pAClldJoW9aUAKOOmxLbuy7Has2bGYk38g8z7uA1V4c
         SwThT6I8FxfNFlIt/hhqD+ca10ArNE9AiQQX4YkINP55xjV99EFUmByJnKfhIKAQlkfC
         CsWJgVhS20jBMckX6eJNTgtkpmFJ8xoTnJ4BN3g20w4HJYpbQseZcYlZBWpAgMDrrLbk
         nyAg==
Received: by 10.180.83.168 with SMTP id r8mr16730712wiy.22.1341142802977;
        Sun, 01 Jul 2012 04:40:02 -0700 (PDT)
Received: from [192.168.178.72] (a83-163-193-240.adsl.xs4all.nl.
 [83.163.193.240])
        by mx.google.com with ESMTPS id t8sm18122883wiy.3.2012.07.01.04.40.01
        (version=TLSv1/SSLv3 cipher=OTHER);
        Sun, 01 Jul 2012 04:40:01 -0700 (PDT)
References: 
 <CAHm08VTAoOmhH_e8PCi2KBiMEc1dPXDEka5q5M-Dhr3Qk17Qvw@mail.gmail.com>
 <CALdd-zjAnYLB2qeo9QDLdOyk9+BQ-_bOvKBMTAKjM=ib5Q=8iw@mail.gmail.com>
 <CAHm08VQSuzMOb+efmT8o9JatuMnWQv2SmvVAOoTcfkXC2R_66A@mail.gmail.com>
 <CALdd-zhPC6WiMVXVRCNCk+3hx8OkN-u=tK+KUcNsVVAodVT+-g@mail.gmail.com>
In-Reply-To: 
 <CALdd-zhPC6WiMVXVRCNCk+3hx8OkN-u=tK+KUcNsVVAodVT+-g@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <8BF9C23E-A62A-46BB-9AC0-61E5078463EB@gmail.com>
Cc: "user@cassandra.apache.org" <user@cassandra.apache.org>,
 "dev@cassandra.apache.org" <dev@cassandra.apache.org>
X-Mailer: iPhone Mail (9B206)
From: Joost Van De Wijgerd <jwijgerd@gmail.com>
Subject: Re: Memtable tuning in 1.0 and higher
Date: Sun, 1 Jul 2012 13:40:00 +0200
To: "dev@cassandra.apache.org" <dev@cassandra.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Jonathan,

Looks good, any chance of porting this fix to the 1.0 branch?

Kind regards

Joost

Sent from my iPhone


On 1 jul. 2012, at 09:25, Jonathan Ellis <jbellis@gmail.com> wrote:

> On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd
> <jwijgerd@gmail.com> wrote:
>> the currentThoughput is increased even before the data is merged into the
>> memtable so it is actually measuring the throughput afaik.
> 
> You're right.  I've attached a patch to
> https://issues.apache.org/jira/browse/CASSANDRA-4399 to fix this.
> 
> -- 
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com