[
https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451592#comment-16451592
]
Anoop Sam John commented on HBASE-20483:
----------------------------------------
In 1.x we have CollectionBackedScanner scanner (very simple) for Snapshots.
When we create a user scan on top of memstore, we have the SegmentScanner kind
of thing. In 2.0 even on snapshot, we have the SegmentScanner. I changed it
back to 1.x way and seems got the same flush perf (with cluster with PE write
workload). And with that, the overall perf for write also almost same as that
of 1.4.4. There were no 512 MB memstore size breach and so sleeps at client
and retry.
> [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)
