hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-15082) Fix merge of MVCC and SequenceID performance regression
Date Wed, 13 Jan 2016 05:03:39 GMT

     [ https://issues.apache.org/jira/browse/HBASE-15082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-15082:
    Attachment: 15082v13.patch

Working on forward-port of the branch-1.1 patch,  I found a bug in this patch and an explanation
for something that baffled me; add fix and doc.

Let me start up some perf comparisons of this patch against what we have currently to see
if the reordering and holding on to mvcc longer changes our perf profile significantly.

> Fix merge of MVCC and SequenceID performance regression
> -------------------------------------------------------
>                 Key: HBASE-15082
>                 URL: https://issues.apache.org/jira/browse/HBASE-15082
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: stack
>            Assignee: stack
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0
>         Attachments: 15082.patch, 15082v10.patch, 15082v12.patch, 15082v13.patch, 15082v2.patch,
15082v2.txt, 15082v3.txt, 15082v4.patch, 15082v5.patch, 15082v6.patch, 15082v7.patch, 15082v8.patch
> This is general fix for increments (appends, checkAnd*) perf-regression identified in
the parent issue. HBASE-15031 has a narrow fix for branch-1.1 and branch-1.0.

This message was sent by Atlassian JIRA

View raw message