[jira] [Commented] (HBASE-16417) In-Memory MemStore Policy for Flattening and Compactions

[Anoop Sam John (JIRA)]

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

Anoop Sam John commented on HBASE-16417:
----------------------------------------

bq. Flat index not only takes less space but is also more friendly for memory 
management which is an advantage.
This is the point u say in the doc "Not ​ ​only ​ ​is ​ ​it ​ ​bigger ​ ​in ​ 
​size ​ ​compared ​ ​to ​ ​a ​ ​flat ​ ​index, ​ ​it ​ ​is ​ ​also ​ 
​fragmented ​ ​whereas ​ ​a ​ ​static ​ ​index
is ​ ​stored ​ ​in ​ ​a ​ ​consecutive ​ ​block ​ ​of ​ ​memory. ​ ​Therefore, 
​ ​flat ​ ​storage ​ ​incurs ​ ​smaller ​ ​overhead ​ ​in
terms ​ ​of ​ ​allocation, ​ ​GC, ​ ​".  (?)
So ur tests are with MSLAB feature turned OFF right?  Some time back in a jira 
it was mentioned so.   So here u speak abt the entry objects to CSLM vs the 
consecutive ref objects in the CellArray?

> 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: 3.0.0
>
>         Attachments: HBASE-16417 - Adaptive Compaction Policy - 20171001.pdf, 
> HBASE-16417 - parameter tuning - 20171001.pdf, HBASE-16417-V01.patch, 
> HBASE-16417-benchmarkresults-20161101.pdf, 
> HBASE-16417-benchmarkresults-20161110.pdf, 
> HBASE-16417-benchmarkresults-20161123.pdf, 
> HBASE-16417-benchmarkresults-20161205.pdf, 
> HBASE-16417-benchmarkresults-20170309.pdf, 
> HBASE-16417-benchmarkresults-20170317.pdf, HBASE-16417.01.patch, 
> HBASE-16417.02.patch, HBASE-16417.03.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)