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 2019/09/23 04:56:00 UTC
[jira] [Commented] (HBASE-16213) A new HFileBlock structure for
fast random get
[ https://issues.apache.org/jira/browse/HBASE-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935555#comment-16935555 ]
stack commented on HBASE-16213:
-------------------------------
HBASE-23055 will allow being able to set DataBlockEncoding.ROW_INDEX_V1 on hbase:meta.
> A new HFileBlock structure for fast random get
> ----------------------------------------------
>
> Key: HBASE-16213
> URL: https://issues.apache.org/jira/browse/HBASE-16213
> Project: HBase
> Issue Type: New Feature
> Components: Performance
> Reporter: binlijin
> Assignee: binlijin
> Priority: Major
> Fix For: 1.4.0, 2.0.0
>
> Attachments: HBASE-16213-master_v1.patch, HBASE-16213-master_v3.patch, HBASE-16213-master_v4.patch, HBASE-16213-master_v5.patch, HBASE-16213-master_v6.patch, HBASE-16213.branch-1.v1.patch, HBASE-16213.branch-1.v4.patch, HBASE-16213.branch-1.v4.patch, HBASE-16213.patch, HBASE-16213_branch1_v3.patch, HBASE-16213_v2.patch, hfile-cpu.png, hfile_block_performance.pptx, hfile_block_performance2.pptx, hfile_block_performance_E2E.pptx
>
>
> HFileBlock store cells sequential, current when to get a row from the block, it scan from the first cell until the row's cell.
> The new structure store every row's start offset with data, so it can find the exact row with binarySearch.
> I use EncodedSeekPerformanceTest test the performance.
> First use ycsb write 100w data, every row have only one qualifier, and valueLength=16B/64/256B/1k.
> Then use EncodedSeekPerformanceTest to test random read 1w or 100w row, and also record HFileBlock's dataSize/dataWithMetaSize in the encoding.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)