Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 B84601050D for ; Fri, 25 Oct 2013 05:03:59 +0000 (UTC) Received: (qmail 4256 invoked by uid 500); 25 Oct 2013 05:03:54 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 4204 invoked by uid 500); 25 Oct 2013 05:03:54 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 4196 invoked by uid 99); 25 Oct 2013 05:03:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 05:03:54 +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 yuzhihong@gmail.com designates 209.85.220.50 as permitted sender) Received: from [209.85.220.50] (HELO mail-pa0-f50.google.com) (209.85.220.50) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 25 Oct 2013 05:03:46 +0000 Received: by mail-pa0-f50.google.com with SMTP id fb1so3192882pad.9 for ; Thu, 24 Oct 2013 22:03:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=OaLeyyGfjHL2btoEGw81BTpmciuCySRP7u38cS6WRj0=; b=jykwbjeTf/zfyNxJSHaMcTYPBDhO9sWfyzcYR90LgJ0bdQwOPR7xVKMJ+GzABYAn2R 5fFKXFLyWOzIJ281hay2JXAOsKFLFwJrHTAnENtd2pKYv/ZGmsq/Z+D8NhkB0wzhREwn QhoiZP+GKaM4Uu+5Lt+nW5w33jofMMzl4KtRZwna6qJRoH+EHueKamzRAzzMCRTSD5xL sdZbSZOg7iGfiWTOeSczfU/Wr6e4iiS3NJBdWtIUnx5ozUt8RltYBu6xlkyuP6NsEQp5 frUKaWm6akT2scV6hC7/zwLZQ47aY3CJR1v2TRvQVE0oMe8e/63ZUDqP3c+M75n6BdTH /dcQ== X-Received: by 10.66.186.204 with SMTP id fm12mr570998pac.189.1382677405679; Thu, 24 Oct 2013 22:03:25 -0700 (PDT) Received: from [192.168.0.10] (c-24-130-233-55.hsd1.ca.comcast.net. [24.130.233.55]) by mx.google.com with ESMTPSA id hu10sm6531386pbc.11.2013.10.24.22.03.23 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Oct 2013 22:03:24 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: Cc: "user@hbase.apache.org" X-Mailer: iPhone Mail (10B146) From: Ted Yu Subject: Re: Linear Scalability in HBase Date: Thu, 24 Oct 2013 22:03:21 -0700 To: "user@hbase.apache.org" X-Virus-Checked: Checked by ClamAV on apache.org How many YCSB clients were used in each setting ? Thanks On Oct 24, 2013, at 9:45 PM, Ramu M S wrote: > Hi All, > > I am running HBase 0.94.6 with 8 region servers and getting throughput of > around 15K Read OPS and 20K Write OPS per server through YCSB tests. Table > is pre created with 8 regions per region server and it has 120 million > records of 700 bytes each. > > I increased the number of region servers to 25, pre created table with 8 > regions per region server and loaded 375 Million records. I'm getting a > throughput of 12K Read OPS and 19K Write OPS per server. A drop of 20% per > server for read and drop of 10% per server for write. > > Distribution of load on region servers is even in all region server in both > scenarios for read and write. > > I wanted to understand if HBase does scale performance linearly? Any > configurations I'm missing? Any factors that might affect this linear > scalability? > > Regards, > Ramu