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 DEC5DF9BC for ; Wed, 3 Apr 2013 16:37:23 +0000 (UTC) Received: (qmail 65926 invoked by uid 500); 3 Apr 2013 16:35:54 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 65650 invoked by uid 500); 3 Apr 2013 16:35:52 -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 59451 invoked by uid 99); 3 Apr 2013 16:31:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 16:31:12 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tyler@datastax.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-la0-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Apr 2013 16:31:06 +0000 Received: by mail-la0-f47.google.com with SMTP id fj20so1631517lab.34 for ; Wed, 03 Apr 2013 09:30:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=gfzr6nr3YEsoVm8EpG2L5Jstko7TZhZvZT5hgVh4F2I=; b=bJm13JZS5mxJW2W9EGj8iBPFyfJj1MPUtUQ2bFbpgE+G57/LVDDKKy+BcESXJz3G88 fti30KQydNBK1ph2A6032ytY2XKcKWMMCL9NidtQBuTrjbKHxItmakdCBJLPVHxmZ235 hleeYTE+1ZAnDLQ3nT2BpujHI8fxhA8wLg1njkEZ3EWCI0mmN1Dkg9WZOBcgS6/lxeS0 r2sEcrll+DaUZTy2bdCVVKaXyPVLHq9l2SxD3IlXicFDv0Ii9ERzFt6cT0kHZR33gnR+ X17FnNQiXKf8lrIFvYQq07EeeA49dlf39ra63MvVOvWsTDN/156j4G4yCnWpDrQ3+Qr8 jAHg== MIME-Version: 1.0 X-Received: by 10.112.59.104 with SMTP id y8mr1475919lbq.39.1365006644208; Wed, 03 Apr 2013 09:30:44 -0700 (PDT) Received: by 10.112.32.99 with HTTP; Wed, 3 Apr 2013 09:30:44 -0700 (PDT) In-Reply-To: References: Date: Wed, 3 Apr 2013 11:30:44 -0500 Message-ID: Subject: Re: Linear scalability problems From: Tyler Hobbs To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=e89a8f83abd724ef3c04d977609d X-Gm-Message-State: ALoCoQnWfoxezx5xi3ELkCM2BaD1dEKr+2Y6PnhyEPbhq4NhDS9I6fwb2uNDVBNQpeMzXQ0u7Ce9 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f83abd724ef3c04d977609d Content-Type: text/plain; charset=ISO-8859-1 If I had to guess, I would say that your client is the bottleneck, not the cluster. Are you inserting data with multiple threads or processes? On Wed, Apr 3, 2013 at 8:49 AM, Anand Somani wrote: > Hi, > > I am running some tests trying to scale out our application from using a 3 > node cluster to 6 node cluster. The thing I observed is that when using a 3 > node cluster I was able to handle abt 41 req/second, so I added 3 more > nodes thinking it should close to double, but instead it only goes upto bat > 47 req/second!! I am doing something wrong and it is not obvious, so wanted > some help in what stats could/should I monitor to tell me things like if a > node has more requests or if the load distribution is not random enough? > > Note I am using direct thrift (old code base) and cassandra 1.1.6. The > data model is for storing blobs (split across columns) and has around 6 CF, > RF=3 and all operations are at quorum. Also at the end of the run nodetool > ring reports the same data size. > > Thanks > Anand > -- Tyler Hobbs DataStax --e89a8f83abd724ef3c04d977609d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
If I had to guess, I would say that your client is the bot= tleneck, not the cluster.=A0 Are you inserting data with multiple threads o= r processes?


On Wed, Apr 3, 2013 at 8:49 AM, Anand Somani <meatforums@gmail.com= > wrote:
Hi,

I am running some tests trying to scale out our appl= ication from using a 3 node cluster to 6 node cluster. The thing I observed= is that when using a 3 node cluster I was able to handle abt 41 req/second= , so I added 3 more nodes thinking it should close to double, but instead i= t only goes upto bat 47 req/second!! I am doing something wrong and it is n= ot obvious, so wanted some help in what stats could/should I monitor to tel= l me things like if a node has more requests or if the load distribution is= not random enough?

Note I am using direct thrift (old code base) and cassa= ndra 1.1.6. The data model is for storing blobs (split across columns) and = has around 6 CF, RF=3D3 and all operations are at quorum. Also at the end o= f the run nodetool ring reports the same data size.

Thanks
Anand



--
Tyler Hobbs
DataStax
--e89a8f83abd724ef3c04d977609d--