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 6E87210056 for ; Tue, 4 Mar 2014 13:27:11 +0000 (UTC) Received: (qmail 21469 invoked by uid 500); 4 Mar 2014 13:27:06 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 21417 invoked by uid 500); 4 Mar 2014 13:27:05 -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 21397 invoked by uid 99); 4 Mar 2014 13:27:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 13:27:03 +0000 X-ASF-Spam-Status: No, hits=2.6 required=5.0 tests=FORGED_YAHOO_RCVD,FREEMAIL_ENVFROM_END_DIGIT,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 13:26:57 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WKpMi-0000xV-Gl for user@hbase.apache.org; Tue, 04 Mar 2014 05:26:36 -0800 Date: Tue, 4 Mar 2014 05:26:36 -0800 (PST) From: shapoor To: user@hbase.apache.org Message-ID: <1393939596404-4056621.post@n3.nabble.com> Subject: heavy reads MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello, i have an application which does a lot of sequential reads. I also save more data, meaning the reads always have to be done in bigger amount of data in storage (writes and reads don't happen parallel). To see how the hbase installation reacts to my needs, I evaluated the reads and calculated out the min- max- average read time. There is often a huge gap between max and mins and also the average does not stay contantly during the process. Why does my hbase behave like this? should I change something in the configuration? regards, forum.png -- View this message in context: http://apache-hbase.679495.n3.nabble.com/heavy-reads-tp4056621.html Sent from the HBase User mailing list archive at Nabble.com.