hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Wed, 01 Mar 2017 12:09:45 GMT

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

ramkrishna.s.vasudevan commented on HBASE-16417:

bq.Value size is set to 100B and number of columns is set to 50. As Duo Zhang mentioned it
could be that the size of value plus size of key is overall >200B, especially given the
number of columns.
Ya right. Same with default also. So with 50 cols you will have each with 100B.
bq.In NONE (which is the current default in master) I see a reduction in the overall wal size
from 203GB with synchronous WAL to 189GB with async wal. Its more than 5% reduction in WAL
Need to check this.

> In-Memory MemStore Policy for Flattening and Compactions
> --------------------------------------------------------
>                 Key: HBASE-16417
>                 URL: https://issues.apache.org/jira/browse/HBASE-16417
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Anastasia Braginsky
>            Assignee: Eshcar Hillel
>             Fix For: 2.0.0
>         Attachments: HBASE-16417-benchmarkresults-20161101.pdf, HBASE-16417-benchmarkresults-20161110.pdf,
HBASE-16417-benchmarkresults-20161123.pdf, HBASE-16417-benchmarkresults-20161205.pdf

This message was sent by Atlassian JIRA

View raw message