Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 8 Jun 2016 08:54:20 +0000 (UTC)
From: "ramkrishna.s.vasudevan (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12975372.1464926180000.25279.1465376060981@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) Fix memstore size estimates to be
 more tighter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 08 Jun 2016 08:54:23 -0000


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

ramkrishna.s.vasudevan commented on HBASE-15950:
------------------------------------------------

These changes are also based on JOL
{code}
long prealign_size = OBJECT + coeff[0] + coeff[2] * REFERENCE;
{code}
{code}
ARRAYLIST = align(OBJECT + REFERENCE + (2 * Bytes.SIZEOF_INT)) + align(ARRAY);
{code}
Rest looks great. The improvement is very significant. 


> Fix memstore size estimates to be more tighter
> ----------------------------------------------
>
>                 Key: HBASE-15950
>                 URL: https://issues.apache.org/jira/browse/HBASE-15950
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 2.0.0
>
>         Attachments: Screen Shot 2016-06-02 at 8.48.27 PM.png, hbase-15950-v0.patch
>
>
> 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)