hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eshcar Hillel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions
Date Tue, 28 Feb 2017 19:48:46 GMT

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

Eshcar Hillel commented on HBASE-16417:
---------------------------------------

I am running YCSB, size of values is set to 100B.

I checked and there is no double logging, so this is the correct data size written to WAL.
>From inspecting the number of entries in each WAL file it turns out that each entry takes
~200B. It could be that the size of the metadata per entry is ~100B, so when the values are
big this is insignificant but with small value the amplification is significant. 

> 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
(v6.3.15#6346)

Mime
View raw message