[
https://issues.apache.org/jira/browse/HBASE-20483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16472866#comment-16472866
]
stack commented on HBASE-20483:
-------------------------------
[~anastas] HBASE-20411 removes the worst 'locking' offender in the write-path.
There are other 'frictions' but this one overwhelmed the others. It does not
make for much of an improvement in throughput; that is an ongoing project (IMC
is not the problem; IMC is unable to shine, in my opinion, until we figure this
basic perf drop-off).
Yes, MSLAB is on in 1.4.
If you want to follow-along,
https://docs.google.com/document/d/1vZ_k6_pNR1eQxID5u1xFihuPC7FkPaJQW8c4M5eA2AQ/edit
is where I"m doing my investigations (HBASE-20188). Thanks.
> [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:
> 0001-HBASE-20483-perpertual-flush-and-memstore-fill-branch-2.0.patch,
> 0001-HBASE-20483-perpetual-flush.branch-1.4.patch,
> 0001-HBASE-20483-perpetual-flush.branch-1.4.patch,
> 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)
