[ https://issues.apache.org/jira/browse/HBASE-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14972390#comment-14972390 ]
Lars Hofhansl commented on HBASE-14613: --------------------------------------- Hmm... Nothing in this thread represented a convincing argument that we should keep it. ;) Reuse is no indication that the GC would not do better (and the increase young collections indicate an issue), and performance was unaffected as I had predicted. Anyway, we can leave it in as long as it remains default off. -1 on turning this always on by default, though. > 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)