hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15046) Perf test doing all mutation steps under row lock
Date Wed, 30 Dec 2015 07:15:49 GMT

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

Lars Hofhansl commented on HBASE-15046:
---------------------------------------

Hey [~stack]. I'm very interested in this. Wanna huddle first thing next year?

I've also written a simple load tester for a kind of workload we have, which essentially overrides
(i.e. writes new versions of) the same keys (row key + CF + CQ) over and over again in batches;
it's likely multiple threads/clients will touch the same key in a batch.


> 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)

Mime
View raw message