You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2013/03/20 05:11:15 UTC
[jira] [Commented] (HBASE-8151) Small optimization in HFileReaderV2
[ https://issues.apache.org/jira/browse/HBASE-8151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607257#comment-13607257 ]
stack commented on HBASE-8151:
------------------------------
+1 on simple patch
> Small optimization in HFileReaderV2
> -----------------------------------
>
> Key: HBASE-8151
> URL: https://issues.apache.org/jira/browse/HBASE-8151
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Attachments: 8151-0.94.txt
>
>
> HFiles V2 store the memstoreTS of each KV.
> In many cases all the KVs in an HFile will have a memstoreTS of 0 (that is the case when at the time the HFile was written there are no KVs that were created after the oldest still active scanner - which is frequently the case).
> In that case we:
> # do not need to decode the memstoreTS (a vlong), since we know its value is 0 and its length is 1 byte.
> # when we compact HFiles and all of the involved files have only KVs with memstoreTS = 0 we know ahead of time that all KVs meet this condition and we do not need to store the memstoreTS in the new HFile.
> This issue will cover the first part. The performance improvement will be modest as it is fairly cheap to decode vlongs of size 1.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira