You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Anastasia Braginsky (JIRA)" <ji...@apache.org> on 2018/05/08 12:02:00 UTC

[jira] [Commented] (HBASE-20483) [PERFORMANCE] Flushing is 2x slower in hbase2.

    [ https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467304#comment-16467304 ] 

Anastasia Braginsky commented on HBASE-20483:
---------------------------------------------

Do you get the same flush performance when working with CCM/CAM/NONE?

> [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)