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 3041D10D2C for ; Wed, 5 Mar 2014 08:27:27 +0000 (UTC) Received: (qmail 72475 invoked by uid 500); 5 Mar 2014 08:27:24 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 71753 invoked by uid 500); 5 Mar 2014 08:27:23 -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 71745 invoked by uid 99); 5 Mar 2014 08:27:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2014 08:27:20 +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 (athena.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; Wed, 05 Mar 2014 08:27:15 +0000 Received: from ben.nabble.com ([192.168.236.152]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WL7AE-0008Ei-IC for user@hbase.apache.org; Wed, 05 Mar 2014 00:26:54 -0800 Date: Wed, 5 Mar 2014 00:26:54 -0800 (PST) From: shapoor To: user@hbase.apache.org Message-ID: <1394008014553-4056695.post@n3.nabble.com> In-Reply-To: <2AE2D589-913E-4B6A-BE0A-1BB0785783AB@gmail.com> References: <1393939596404-4056621.post@n3.nabble.com> <2AE2D589-913E-4B6A-BE0A-1BB0785783AB@gmail.com> Subject: Re: 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 I read that pre-splitting the table is for write-maintenance. I haven't still splitted. I have heavier writes than reads but as mentioned they don't occur parallel. It's either read or write. My application is running on a "single node" hbase-0.94.16.tar installation. Thanks and regards, -- View this message in context: http://apache-hbase.679495.n3.nabble.com/heavy-reads-tp4056621p4056695.html Sent from the HBase User mailing list archive at Nabble.com.