You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2016/01/11 08:11:39 UTC

[jira] [Commented] (HBASE-14613) Remove MemStoreChunkPool?

    [ https://issues.apache.org/jira/browse/HBASE-14613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15091531#comment-15091531 ] 

Lars Hofhansl commented on HBASE-14613:
---------------------------------------

Should I close this one?

Lately I've also been debating trying G1 without _any_ SLAB allocation and see how that's doing. It would save us copying the backing data for every single Cell upon writing into the memstore. (all in to the tune of "Don't try to outsmart the GC" - imagine a Beachboys tune to this :) )

> 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)