[
https://issues.apache.org/jira/browse/HBASE-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15320054#comment-15320054
]
Anoop Sam John commented on HBASE-15950:
----------------------------------------
Great
So how the object size estimates looks like now? (For a KV added into CSLM)
bq.if (UnsafeAccess.theUnsafe != null
Use UnsafeAvailChecker#isAvailable() instead. If we use UnsafeAccess.theUnsafe
directly, it might try to load the class Unsafe and that may throw
ClassNotFoundException. UnsafeAvailChecker wont have this issue.
Other than that looks good.
> 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)
