[
https://issues.apache.org/jira/browse/HBASE-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972393#comment-14972393
]
stack commented on HBASE-14613:
-------------------------------
Smile.
bq. Nothing in this thread represented a convincing argument that we should
keep it.
There is a marked drop in CMS GC time.
bq. ... and the increase young collections indicate an issue
Need to figure it out. Turn on more flags to see they why. My guess is my
aggressive up-sizing of the pool. TBD.
Was going to poke at this some more in a while...
> 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, gc.png, writes.png
>
>
> 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)
