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-14919) Infrastructure refactoring for In-Memory Flush
Date Thu, 11 Feb 2016 18:37:18 GMT

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

stack commented on HBASE-14919:

I'm going to commit. If objection, shout and I'll revert.

I ran comparison ycsb loadings of raw master branch against master with this patch. Numbers
come out close enough (with patch 50/50 does better but not as well in the 20/80 write scenario).
I looked at a running ycsb 20/80% writes with profiler and the ugly stuff is not from this

Related, I tried backporting to 1.2 because thats what my rig  had running but its not an
easy task mostly because of where we pass CellComparator in master and KeyValue.KVComparator
in branch.

> Infrastructure refactoring for In-Memory Flush
> ----------------------------------------------
>                 Key: HBASE-14919
>                 URL: https://issues.apache.org/jira/browse/HBASE-14919
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: 2.0.0
>            Reporter: Eshcar Hillel
>            Assignee: Eshcar Hillel
>         Attachments: HBASE-14919-V01.patch, HBASE-14919-V01.patch, HBASE-14919-V02.patch,
HBASE-14919-V03.patch, HBASE-14919-V04.patch, HBASE-14919-V04.patch, HBASE-14919-V05.patch,
HBASE-14919-V06.patch, HBASE-14919-V06.patch, HBASE-14919-V07.patch, HBASE-14919-V08.patch,
HBASE-14919-V09.patch, HBASE-14919-V10.patch, HBASE-14919-V11.patch, HBASE-14919-V12.patch
> Refactoring the MemStore hierarchy, introducing segment (StoreSegment) as first-class
citizen and decoupling memstore scanner from the memstore implementation.

This message was sent by Atlassian JIRA

View raw message