[
https://issues.apache.org/jira/browse/HBASE-7495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555956#comment-13555956
]
liang xie commented on HBASE-7495:
----------------------------------
[~lhofhansl], for "get" operation, the code should go to "seek", not
"requestSeek", please correct me if anything wrong
[~zjushch], IMHO, it's easier to see the improment if the test:1)larger test
dataset and smaller cache size 2)more numberOfStorefiles/disks 3)not too heavy
IO-bound(e.g. 100% io util)
the patch is broken some test cases, i'll look into it later
> parallel scanner seek in StoreScanner's constructor
> ---------------------------------------------------
>
> Key: HBASE-7495
> URL: https://issues.apache.org/jira/browse/HBASE-7495
> Project: HBase
> Issue Type: Bug
> Components: Scanners
> Affects Versions: 0.94.3, 0.96.0
> Reporter: liang xie
> Assignee: liang xie
> Attachments: HBASE-7495.txt
>
>
> seems there's a potential improvable space before doing scanner.next:
> {code:title=StoreScanner.java|borderStyle=solid}
> if (explicitColumnQuery && lazySeekEnabledGlobally) {
> for (KeyValueScanner scanner : scanners) {
> scanner.requestSeek(matcher.getStartKey(), false, true);
> }
> } else {
> for (KeyValueScanner scanner : scanners) {
> scanner.seek(matcher.getStartKey());
> }
> }
> {code}
> we can do scanner.requestSeek or scanner.seek in parallel, instead of current
> serialization, to reduce latency for special case.
> Any ideas on it ? I'll have a try if the comments/suggestions are positive：）
--
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
