You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2017/03/01 02:23:45 UTC
[jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for
Flattening and Compactions
[ https://issues.apache.org/jira/browse/HBASE-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15889368#comment-15889368 ]
ramkrishna.s.vasudevan commented on HBASE-16417:
------------------------------------------------
By default YCSB creates rows of 1K size with 10 cols and each having 100B of value and with meta data each row will be > 1K.
Though in YCSB you specify 100G what is the number of records? May be that is the reason.
How ever why EAGER reduces the size to 124G should be investigated may be the truncation is the reason how ever it is good to debug.
> 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)