Return-Path: 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 07D8E18C68 for ; Wed, 29 Jul 2015 20:53:29 +0000 (UTC) Received: (qmail 52830 invoked by uid 500); 29 Jul 2015 20:53:26 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 52790 invoked by uid 500); 29 Jul 2015 20:53:26 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 52780 invoked by uid 99); 29 Jul 2015 20:53:26 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 20:53:26 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 98377193C2B for ; Wed, 29 Jul 2015 20:53:25 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3 X-Spam-Level: *** X-Spam-Status: No, score=3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nATNWM_zv_Nq for ; Wed, 29 Jul 2015 20:53:13 +0000 (UTC) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id A180143818 for ; Wed, 29 Jul 2015 20:53:12 +0000 (UTC) Received: by lahh5 with SMTP id h5so13598974lah.2 for ; Wed, 29 Jul 2015 13:53:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=yPCyJoj5faRBkI03hRO5Wvbiz7dm3ghyD4bVdgu4EDo=; b=KB9xOAHyCkJfJ0gnta6DrcGFhuihw9OdQH0Y/IcdU0HERwIOCumOzmeMNrZDQD7GVz Ifo4pxYFY23Skc3G837jrThvgVSiSrh+eOKIQGGI5yCZWLQ2xrYEP3qqzG8imjAyO7Gj yH2TUn5Zje3ozk7cTlofp8QpjuGcXHwF75+dhB+k04kx4PNpFjSFUgt9ZXrZ9qjBODuQ AIum/EmDngXxRsP0bQwf5OaPNvI+tczNMaNp3b1B86J0M9h4UBiHWgrU53sxRcH2I/gK MM5RuSFtRSP8IitnB07gXc6Nn5svVos84YUTXTOPsIffcUtBzWEgwaICmagujeakeyya u0RQ== X-Gm-Message-State: ALoCoQmhhCNpySPWjlpkwQAZqPv9JCO56qlBfpMxQukKMH1IWdnySewlyAQnzdeYNNkklAbNn8Gs X-Received: by 10.112.158.4 with SMTP id wq4mr1875765lbb.106.1438203185128; Wed, 29 Jul 2015 13:53:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.25.83.72 with HTTP; Wed, 29 Jul 2015 13:52:45 -0700 (PDT) In-Reply-To: References: From: Soerian Lieve Date: Wed, 29 Jul 2015 13:52:45 -0700 Message-ID: Subject: Re: Reduced write performance when reading To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c25f80f70221051c09c53e --001a11c25f80f70221051c09c53e Content-Type: text/plain; charset=UTF-8 Found the problem, it turns out that what Bharatendra suggested was correct. I had set the memtable_flush_writers to equal the number of cores but hadn't restarted the Cassandra process, so they didn't take the configuration. On Wed, Jul 29, 2015 at 12:59 PM, Robert Coli wrote: > On Tue, Jul 28, 2015 at 4:49 PM, Soerian Lieve > wrote: > >> I did already set that to the number of cores of the machines (24), but >> it made no difference. >> > > I continue to suggest that you file a JIRA ticket... I feel you have done > sufficient community based due dilligence to question whether this > performance is expected on the server side. You have a repro path to > illustrate the behavior. Why not file a JIRA? > > (and respond on thread with its url...) > > =Rob > > --001a11c25f80f70221051c09c53e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Found the problem, it turns out that what=C2=A0Bharatendra= suggested was correct.=C2=A0
I had set the memtable_flush_writers to e= qual the number of cores but hadn't restarted the Cassandra process, so= they didn't take the configuration.=C2=A0

On Wed, Jul 29, 2015 at 12:59 PM, = Robert Coli <rcoli@eventbrite.com> wrote:
On Tue, Jul 28, 2015 at 4:49 PM, Soerian = Lieve <slieve@liveramp.com> wrote:
I did already set that to the number of core= s of the machines (24), but it made no difference.
<= br>
I continue to suggest that you file a JIRA ticket... I= feel you have done sufficient community based due dilligence to question w= hether this performance is expected on the server side. You have a repro pa= th to illustrate the behavior. Why not file a JIRA?

(and respond on thread with its url...)

=3DRob
=C2=A0

--001a11c25f80f70221051c09c53e--