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

stack edited comment on HBASE-20411 at 4/16/18 6:34 PM:
--------------------------------------------------------

2.simple.patch.69074.lock.svg is what our locking profile looks like after this 
patch has been applied. Blocking on MutableSegment has been removed (It does 
not show in this svg and in jfr, it no longer shows up in events or in 
'contention' list). We are left with the Semaphore on RPC scheduling and mvcc 
completion (This makes our locking profile looks like 1.2.7 again <= This 
statement is wrong; in 1.2.7 our locking profile does not have the rpc 
semaphore; it has the mvcc completion and then a bunch of blocking in dfsclient 
that we don't have in 2.0.0).

Not much by way of throughput improvement after this goes in.


was (Author: stack):
2.simple.patch.69074.lock.svg is what our locking profile looks like after this 
patch has been applied. Blocking on MutableSegment has been removed. We are 
left with the Semaphore on RPC scheduling and mvcc completion (This makes our 
locking profile looks like 1.2.7 again <= This statement is wrong; in 1.2.7 our 
locking profile does not have the rpc semaphore; it has the mvcc completion and 
then a bunch of blocking in dfsclient that we don't have in 2.0.0).

Not much by way of throughput improvement after this goes in.

> 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, 41901.lock.svg, 
> 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
>
>
> 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)

Reply via email to