[
https://issues.apache.org/jira/browse/HBASE-20411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466830#comment-16466830
]
stack commented on HBASE-20411:
-------------------------------
Running on cluster with this patch, there is before
[^2.pe.write.32026.lock.svg] , where the only lock that shows is the
MutableSegment increment lock and then after,
[^2.pe.write.ameliorate.106553.lock.svg] , where we have a bunch of different
locks showing up. Here is how this MutableSegment lock shows in
!jmc6.write_time_locks.png!
> Ameliorate MutableSegment synchronize
> -------------------------------------
>
> Key: HBASE-20411
> URL: https://issues.apache.org/jira/browse/HBASE-20411
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Major
> Attachments: 2.load.patched.17704.lock.svg,
> 2.load.patched.2.17704.lock.svg, 2.more.patch.12010.lock.svg,
> 2.pe.write.32026.lock.svg, 2.pe.write.ameliorate.106553.lock.svg,
> 41901.lock.svg, HBASE-20411-atomiclong-longadder.patch,
> HBASE-20411.branch-2.0.001.patch, HBASE-20411.branch-2.0.002.patch,
> HBASE-20411.branch-2.0.003.patch, HBASE-20411.branch-2.0.004.patch,
> HBASE-20411.branch-2.0.005.patch, HBASE-20411.branch-2.0.006.patch,
> HBASE-20411.branch-2.0.007.patch, HBASE-20411.branch-2.0.008.patch,
> HBASE-20411.branch-2.0.009.patch, HBASE-20411.branch-2.0.010.patch,
> jmc6.write_time_locks.png
>
>
> This item is migrated from HBASE-20236 so it gets dedicated issue.
> Let me upload evidence that has this synchronize as a stake in our write-time
> perf. I'll migrate the patch I posted with updates that come of comments
> posted by [~mdrob] on the HBASE-20236 issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
