hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-1590) Extend TestHeapSize and ClassSize to do "deep" sizing of Objects
Date Sun, 08 Jun 2014 21:55:03 GMT

     [ https://issues.apache.org/jira/browse/HBASE-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell resolved HBASE-1590.
-----------------------------------

    Resolution: Won't Fix

Stale issue. Reopen if still relevant (if there's new activity)

> Extend TestHeapSize and ClassSize to do "deep" sizing of Objects
> ----------------------------------------------------------------
>
>                 Key: HBASE-1590
>                 URL: https://issues.apache.org/jira/browse/HBASE-1590
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 0.20.0
>            Reporter: Jonathan Gray
>            Assignee: stack
>            Priority: Minor
>
> As discussed in HBASE-1554 there is a bit of a disconnect between how ClassSize calculates
the heap size and how we need to calculate heap size in our implementations.
> For example, the LRU block cache can be sized via ClassSize, but it is a shallow sizing.
 There is a backing ConcurrentHashMap that is the largest memory consumer.  However, ClassSize
only counts that as a single reference.  But in our heapSize() reporting, we want to include
*everything* within that Object.
> This issue is to resolve that dissonance.  We may need to create an additional ClassSize.estimateDeep(),
we may need to rethink our HeapSize interface, or maybe just leave it as is.  The two primary
goals of all this testing is to 1) ensure that if something is changed and the sizing is not
updated, our tests fail, and 2) ensure our sizing is as accurate as possible.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message