You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/12/30 07:49:49 UTC
[jira] [Updated] (HBASE-15046) Perf test doing all mutation steps
under row lock
[ https://issues.apache.org/jira/browse/HBASE-15046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-15046:
--------------------------
Attachment: 1.2.svg
1.2.v2.svg
Here is what a RS looks like when YCSB write only is being run against it. Two samples.
Trying to change ordering but this doMiniBatchMutation has a lot going on. First few attempts have me locked up. Will keep at it.
> Perf test doing all mutation steps under row lock
> -------------------------------------------------
>
> Key: HBASE-15046
> URL: https://issues.apache.org/jira/browse/HBASE-15046
> Project: HBase
> Issue Type: Sub-task
> Components: Performance
> Reporter: stack
> Attachments: 1.2.svg, 1.2.v2.svg
>
>
> This issue is about perf testing a redo of the write pipeline so that rather than:
> * take rowlock
> * start mvcc
> * append to WAL
> * add to memstore
> * sync WAL
> * let go of rowlock
> * finish up mvcc
> instead.... try...
> * take rowlock
> * start mvcc
> * append to WAL
> * sync WAL
> * add to memstore
> * finish up mvcc
> * let go of rowlock
> The latter is more straight-forward undoing need of rolling back memstore if all does not succeed.
> It might be slower though. This issue is a look-see/try it.
> The redo will also help address the parent issue in a more general way so we can do without the special-casing done for branch-1.0 and branch-1.1 done in a sibling subtask.
> Other benefits are that the current write pipeline is copy/pasted in a few places -- in append, increment and checkand* -- and a refactor will allow us to fix this duplication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)