[
https://issues.apache.org/jira/browse/HBASE-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14961041#comment-14961041
]
stack commented on HBASE-14613:
-------------------------------
Now I don't trust what this program is showing us. I wanted to find where
exactly the boundary between allocate in old gen and allocate in eden is for
CMS so I just kept adding 256k to the size and this is what the program spewed:
{code}
Allocation in Eden: 62652416 (capacity: 282066944)
Allocation in Eden: 62914560 (capacity: 282066944)
Allocation in Eden: 63176704 (capacity: 282066944)
GC in PS Scavenge
Allocation in Eden: 63438848 (capacity: 274202624)
Allocation in Eden: 63700992 (capacity: 274202624)
Allocation in Eden: 63963136 (capacity: 274202624)
GC in PS Scavenge
Allocation in Eden: 64225280 (capacity: 266338304)
Allocation in Eden: 64487424 (capacity: 266338304)
Allocation in Eden: 64749568 (capacity: 266338304)
...
{code}
... and so on.... Let me look at src
> Remove MemStoreChunkPool?
> -------------------------
>
> Key: HBASE-14613
> URL: https://issues.apache.org/jira/browse/HBASE-14613
> Project: HBase
> Issue Type: Brainstorming
> Reporter: Lars Hofhansl
> Priority: Minor
> Attachments: 14613-0.98.txt
>
>
> I just stumbled across MemStoreChunkPool. The idea behind is to reuse chunks
> of allocations rather than letting the GC handle this.
> Now, it's off by default, and it seems to me to be of dubious value. I'd
> recommend just removing it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
