hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16213) A new HFileBlock structure for fast random get
Date Thu, 11 Aug 2016 10:01:20 GMT

    [ https://issues.apache.org/jira/browse/HBASE-16213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416969#comment-15416969

Yu Li commented on HBASE-16213:

Nice work and nice testing. Since still need to wait for our machines to be ready for further
E2E perf testing (due to machine room relocation), I suggest to start code refinement according
to review comments from Ram and others, and update patch on review board [~aoxiang]

btw, would be great to see performance data from your side sir [~stack], thanks.

> 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.patch, HBASE-16213_branch1_v3.patch,
HBASE-16213_v2.patch, hfile-cpu.png, hfile_block_performance.pptx, hfile_block_performance2.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

View raw message