Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@locus.apache.org Received: (qmail 1379 invoked from network); 22 Apr 2008 14:31:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Apr 2008 14:31:27 -0000 Received: (qmail 37511 invoked by uid 500); 22 Apr 2008 14:31:28 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 37496 invoked by uid 500); 22 Apr 2008 14:31:28 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 37485 invoked by uid 99); 22 Apr 2008 14:31:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2008 07:31:28 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [203.99.254.143] (HELO rsmtp1.corp.hki.yahoo.com) (203.99.254.143) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Apr 2008 14:30:34 +0000 Received: from [10.66.70.241] (wifi-postauth-70-241.eglbp.corp.yahoo.com [10.66.70.241]) by rsmtp1.corp.hki.yahoo.com (8.13.8/8.13.8/y.rout) with ESMTP id m3MEUgEP070160 for ; Tue, 22 Apr 2008 07:30:42 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=r4RsrPxz/nQ6k4gIozLdonfB+mjC7x1OSBmalBC60BdacFapxBOY8P0TQ4nRgfEv Message-ID: <480DF692.9010801@yahoo-inc.com> Date: Tue, 22 Apr 2008 20:00:42 +0530 From: Karthik Pattabiraman User-Agent: Thunderbird 2.0.0.12 (Windows/20080213) MIME-Version: 1.0 To: hbase-dev@hadoop.apache.org Subject: HBase Performance question References: <1208873728.15332.ezmlm@hadoop.apache.org> In-Reply-To: <1208873728.15332.ezmlm@hadoop.apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, I am evaluating HBase for a serving system. The requirements are fairly simple. Each record comprises a key and a value (size ~4k). I set up a small cluster consisting of two boxes and the number of records inserted into the table is close to 65K. Now I ran a tomcat server on one of the boxes (where the master is running). The tomcat server establishes a connection to hbase at start and then on each request queries the hbase for the record. The benchmarks were not good. I ran the benchmarks for 30 min with 20 clients (talking to tomcat) and the average response time was 51 ms. When I increased the number of clients to 50, the average response time increased to 110 ms. To ensure that tomcat is not the bottleneck, I logged the time taken for each Hbase request and found that to be correlating the benchmarks (time increased when i increased the number of clients.). Any idea as to why this would happen given that the number of records is not huge? (FYI: Both the boxes act as region servers, the box where tomcat runs, also runs hbase master and the dfs namenode) Could it be due to the way I have set up Hbase? Any help would be appreciated. thanks karthik