hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-20411) Ameliorate MutableSegment synchronize
Date Mon, 16 Apr 2018 18:30:00 GMT

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

stack commented on HBASE-20411:

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).
Not much by way of perf improvement though.

> 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

This message was sent by Atlassian JIRA

View raw message