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 7505311367 for ; Wed, 13 Aug 2014 16:01:48 +0000 (UTC) Received: (qmail 65580 invoked by uid 500); 13 Aug 2014 16:01:46 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 65489 invoked by uid 500); 13 Aug 2014 16:01:46 -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 65470 invoked by uid 99); 13 Aug 2014 16:01:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 16:01:46 +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 (nike.apache.org: domain of ndimiduk@gmail.com designates 209.85.219.51 as permitted sender) Received: from [209.85.219.51] (HELO mail-oa0-f51.google.com) (209.85.219.51) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Aug 2014 16:01:20 +0000 Received: by mail-oa0-f51.google.com with SMTP id o6so8610866oag.24 for ; Wed, 13 Aug 2014 09:01:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=MOqFSkihThtX1Z0oB7IWkdpDjUnoeVBMkD8xo2bM4h8=; b=uB8d/uptaWytTPdmjKf4oQbJlv4JZnSF73JX9gGA+gCJOX+BE6vx5G8TZdKyr4nj35 j0FipHSsPSqEjxTbHX0ZUuWn57CQ77WS8d+ZoHFdhyK1VFeJMI9BQEmKaslUOMRah1SL Uyy03gn7OoNCRzH1GRmpV7hA2nJXZ6ejqIN+Gx6nelVB549DUDHmfjACs8KBzVZX3Ny+ GcT6WSvu2ALuiCG3kZv6XHMlT2cTNKYXLYrr+05CV+caOBYiOB2PTVMe9lGS6T7t1BFo CIKJNPA023Vm4Hcm21jyKBeExsBwr7XbOLjgk0CfXdqxoVcL4Foy/XzqCadtLj6mmWuc K7DA== X-Received: by 10.182.94.204 with SMTP id de12mr4596638obb.66.1407945679328; Wed, 13 Aug 2014 09:01:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.114.163 with HTTP; Wed, 13 Aug 2014 09:00:59 -0700 (PDT) In-Reply-To: References: <752a54dd.41cfa176.53eb8297.3af73@o2.pl> From: Nick Dimiduk Date: Wed, 13 Aug 2014 09:00:59 -0700 Message-ID: Subject: Re: Hbase Read/Write poor performance. Please help! To: hbase-user Content-Type: multipart/alternative; boundary=e89a8f83964f14599b050084e6a4 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f83964f14599b050084e6a4 Content-Type: text/plain; charset=UTF-8 Have you looked at the performance guidelines in our online book? http://hbase.apache.org/book.html#performance http://hbase.apache.org/book.html#casestudies.perftroub On Wed, Aug 13, 2014 at 8:43 AM, Pradeep Gollakota wrote: > Can you post the client code you're using to read/write from HBase? > > > On Wed, Aug 13, 2014 at 11:21 AM, kacperolszewski > wrote: > > > Hello there, I'm running a read/write benchmark on a huge data (tweeter > > posts) for my school project. > > The problem im dealing with is that the tests are going extreamly slow. > > I dont know how to optimize the process. Hbase is using only about 10% of > > RAM memory, and 40% of CPU. > > I've been experimenting with properties of hbase-site.xml file but I > can't > > see any results. I think there is something I need to put in the API's > code. > > It's a single node, local operation. Virtual machine has 8GB RAM. Any > help > > will be appreciated. > > Best Regards - Kacper, student > --e89a8f83964f14599b050084e6a4--