You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yu Li (JIRA)" <ji...@apache.org> on 2017/01/22 09:35:26 UTC

[jira] [Comment Edited] (HBASE-17507) Add document for the mvcc preassign feature introduced in HBASE-16698

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

Yu Li edited comment on HBASE-17507 at 1/22/17 9:35 AM:
--------------------------------------------------------

According to our study and prototype here, mvcc preassign will be some kind of limitation when we try to parallelize WAL sync (IO bound) and mvcc assigning (CPU bound) on write path (SEDA), so let's just keep it configurable for a little bit longer (smile).

And since SEDA will increase throughput (PROS) but also longer RT (CONS), it doesn't mean mvcc preassign will become useless after SEDA is done on write path, just case by case.


was (Author: carp84):
According to our study and prototype here, mvcc preassign will be some kind of limitation when we try to parallelize WAL sync (IO bound) and mvcc assigning (CPU bound) on write path, so let's just keep it configurable for a little bit longer (smile).

> Add document for the mvcc preassign feature introduced in HBASE-16698
> ---------------------------------------------------------------------
>
>                 Key: HBASE-17507
>                 URL: https://issues.apache.org/jira/browse/HBASE-17507
>             Project: HBase
>          Issue Type: Task
>            Reporter: Yu Li
>            Assignee: Yu Li
>
> In this JIRA we will supply a design doc of the mvcc preassign mechanism introduced in HBASE-16698, as well as more detailed performance data of it for better reference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)