Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 3 Jun 2016 04:27:59 +0000 (UTC)
From: "Anoop Sam John (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12975372.1464926180000.22424.1464928079231@Atlassian.JIRA>
In-Reply-To: <JIRA.12975372.1464926180000@Atlassian.JIRA>
References: <JIRA.12975372.1464926180000@Atlassian.JIRA> <JIRA.12975372.1464926180899@arcas>
Subject: [jira] [Commented] (HBASE-15950) We are grossly overestimating the
 memstore size
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 03 Jun 2016 04:28:01 -0000


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

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

When memstore cells are in MSLAB,  ya we  may not need to consider the size of Array (this is 16 bytes per cell)..   But we may need to consider the size of the actual cell bytes length.

> We are grossly overestimating the memstore size
> -----------------------------------------------
>
>                 Key: HBASE-15950
>                 URL: https://issues.apache.org/jira/browse/HBASE-15950
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>             Fix For: 2.0.0
>
>         Attachments: Screen Shot 2016-06-02 at 8.48.27 PM.png
>
>
> While testing something else, I was loading a region with a lot of data. Writing 30M cells in 1M rows, with 1 byte values. 
> The memstore size turned out to be estimated as 4.5GB, while with the JFR profiling I can see that we are using 2.8GB for all the objects in the memstore (KV + KV byte[] + CSLM.Node + CSLM.Index). 
> This obviously means that there is room in the write cache that we are not effectively using. 


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