[
https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451712#comment-16451712
]
stack commented on HBASE-20483:
-------------------------------
I tried putting in place ColelctionBackedScanner. It makes little difference
for me on cluster runs. When I try it in my little rig that just does
continuous flush with DisabledWALProvider, i see that flush runs a little
faster in 2.0.0 with CollectionBackedScanner so thats good (It seems to write
out about same number of edits -- and eventual filesize of 164M -- in about 2.1
seconds where 1.2.7 is taking 2.4 for about same amount).
Need more wins (smile).
> [PERFORMANCE] Flushing is 2x slower in hbase2.
> ----------------------------------------------
>
> Key: HBASE-20483
> URL: https://issues.apache.org/jira/browse/HBASE-20483
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Reporter: stack
> Assignee: stack
> Priority: Major
>
> When flush is slow, memstores backup and go slower. See "1.2.7 vs. 2.0.0
> Flush History"
> https://docs.google.com/spreadsheets/d/1sihTxb4aCplR3Rr_GGXkPlwhMIm-CbB9j_5339AS0Zc/edit#gid=1016758826
> for compare. First noted by [~anoop.hbase]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
