[
https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468342#comment-16468342
]
stack commented on HBASE-20483:
-------------------------------
bq. Is the above CPU usage after the PE patch where you made IMC disabled ?
Because the above command will create table with IMC as you may be knowing
already. Just confirming.
Yeah, its after.
hbase1 seems to flush more data and looking at inbound, there is more being
written into hbase1 (I was thinking that replays or whatever were upping what
was inbound on hbase2). We have few metrics in here, HBASE-20549, so hacking in
some.
> [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
> Attachments: PerpetualFlushingProgram.patch,
> PerpetualFlushingProgram1.2.patch, SnapshotSegmentScanner_2.0.0.patch
>
>
> 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)
