Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 8 Mar 2017 09:53:38 +0000 (UTC)
From: "Allan Yang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13049181.1488957264000.10543.1488966818116@Atlassian.JIRA>
In-Reply-To: <JIRA.13049181.1488957264000@Atlassian.JIRA>
References: <JIRA.13049181.1488957264000@Atlassian.JIRA> <JIRA.13049181.1488957264994@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17757) Unify blocksize after encoding to
 decrease memory fragment
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 08 Mar 2017 09:53:42 -0000


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

Allan Yang commented on HBASE-17757:
------------------------------------

{quote}
How is the default value of 0.5 determined ?
{quote}
it is an empirical value based on our production env. But it also can vary in different scenarios.

> Unify blocksize after encoding to decrease memory fragment 
> -----------------------------------------------------------
>
>                 Key: HBASE-17757
>                 URL: https://issues.apache.org/jira/browse/HBASE-17757
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Allan Yang
>            Assignee: Allan Yang
>         Attachments: HBASE-17757.patch
>
>
> Usually, we store encoded block(uncompressed) in blockcache/bucketCache. Though we have set the blocksize, after encoding, blocksize is varied. Varied blocksize will cause memory fragment problem, which will result in more FGC finally.In order to relief the memory fragment, This issue adjusts the encoded block to a unified size.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)