Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of yuzhihong@gmail.com designates
 209.85.217.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <DC5EBE7F3610EB4CA5C7E92D76873E15180DD42AEA@exchange2007.carrieriq.com>
References: 
 <CAAg3a2oCJh5CL89OGRfkBj0PVJd-U6c1JWpxauLcDfu=BcFk9Q@mail.gmail.com>
	<DC5EBE7F3610EB4CA5C7E92D76873E15180DD42AEA@exchange2007.carrieriq.com>
Date: Sat, 19 Oct 2013 20:33:53 -0700
Message-ID: 
 <CALte62w77dXfC8nKj0t=PnXijV-2LJFGReipYJc7gajr=WZ8jw@mail.gmail.com>
Subject: Re: Beware of PREFIX_TREE block encoding
From: Ted Yu <yuzhihong@gmail.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e0160b7be2c917804e923d6ae

--089e0160b7be2c917804e923d6ae
Content-Type: text/plain; charset=ISO-8859-1

Interesting.

>From this graph (HBASE-4676), PREFIX_TREE block encoding is not sensitive
to variation in block size:
https://issues.apache.org/jira/secure/attachment/12500778/SeeksPerSec%20by%20blockSize.png

What was your block size ?
If you don't bypass StoreScanner/KeyValueHeap, would that make a difference
?

Thanks


On Sat, Oct 19, 2013 at 7:34 PM, Vladimir Rodionov
<vrodionov@carrieriq.com>wrote:

> What I wanted to say by this? HBase still does not have block encoding
> which is optimal for both scan and seek (re-seek).
> I do not think these goals are mutually exclusive.
>
>
> Best regards,
> Vladimir Rodionov
> Principal Platform Engineer
> Carrier IQ, www.carrieriq.com
> e-mail: vrodionov@carrieriq.com
>
> ________________________________________
> From: Vladimir Rodionov [vladrodionov@gmail.com]
> Sent: Saturday, October 19, 2013 7:32 PM
> To: dev@hbase.apache.org
> Subject: Beware of PREFIX_TREE block encoding
>
> The scan performance is bad. 10 x slower on my tests than for blocks with
> NONE encoding. I scan data directly from block cache through
> StoreFileScanner (bypassing all StoreScanner/KeyValueHeap stuff). It should
> be clearly stated  that this encoding degrades overall performance
> significantly in favor of data size reduction and is suitable only for Gets
> - not for Scans.
>
> Best regards,
> -Vladimir Rodionov
>
> -
>
> Confidentiality Notice:  The information contained in this message,
> including any attachments hereto, may be confidential and is intended to be
> read only by the individual or entity to whom this message is addressed. If
> the reader of this message is not the intended recipient or an agent or
> designee of the intended recipient, please note that any review, use,
> disclosure or distribution of this message or its attachments, in any form,
> is strictly prohibited.  If you have received this message in error, please
> immediately notify the sender and/or Notifications@carrieriq.com and
> delete or destroy any copy of this message and its attachments.
>

--089e0160b7be2c917804e923d6ae--