[
https://issues.apache.org/jira/browse/HBASE-18485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113957#comment-16113957
]
Guanghao Zhang commented on HBASE-18485:
----------------------------------------
Ok. Changed type to improvement.
bq. Should we enable the prefetch as default?
Checked HBASE-13071, it was merged since hbase 2.0. So it should be default in
3.0? But we will remove the blocking code and use the async code base. The
async client scanner will do the prefetch job by default. So I thought we don't
need enable it as default in this patch.
> Performance issue: ClientAsyncPrefetchScanner is slower than
> ClientSimpleScanner
> --------------------------------------------------------------------------------
>
> Key: HBASE-18485
> URL: https://issues.apache.org/jira/browse/HBASE-18485
> Project: HBase
> Issue Type: Improvement
> Reporter: Guanghao Zhang
> Assignee: Guanghao Zhang
> Attachments: HBASE-18485-v1.patch, HBASE-18485-v2.patch,
> HBASE-18485-v3.patch, HBASE-18485-v4.patch, HBASE-18485-v4.patch,
> HBASE-18485-v4.patch
>
>
> Copied the test result from HBASE-17994.
> {code}
> ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation --rows=100000
> --nomapred scan 1
> ./bin/hbase org.apache.hadoop.hbase.PerformanceEvaluation --rows=100000
> --nomapred --asyncPrefetch=True scan 1
> {code}
> Mean latency.
> || ||Test1|| Test2 || Test3 || Test4|| Test5||
> |scan| 12.21 | 14.32 | 13.25 | 13.07 | 11.83 |
> |scan with prefetch=True | 37.36 | 37.88 | 37.56 | 37.66 | 38.28 |
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
