[
https://issues.apache.org/jira/browse/HBASE-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432622#comment-15432622
]
Anoop Sam John commented on HBASE-16213:
----------------------------------------
Ya in my initial comments also I was suggesting we can do in new jiras. But
towards end there are lot of duplication. Would be better if the new DBE can
some way extend the NoOp DBE equivalent. Let us know if u need any help.
> 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
> Attachments: HBASE-16213-master_v1.patch,
> HBASE-16213-master_v3.patch, HBASE-16213-master_v4.patch, HBASE-16213.patch,
> HBASE-16213_branch1_v3.patch, HBASE-16213_v2.patch,
> cpu_blocksize_64K_valuelength_16B.png,
> cpu_blocksize_64K_valuelength_256B.png,
> cpu_blocksize_64K_valuelength_64B.png, hfile-cpu.png,
> hfile_block_performance.pptx, hfile_block_performance2.pptx,
> new-hfile-block.xlsx, qps_blocksize_64K_valuelength_16B.png,
> qps_blocksize_64K_valuelength_256B.png, qps_blocksize_64K_valuelength_64B.png
>
>
> 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
(v6.3.4#6332)
