hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliott Clark (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14613) Remove MemStoreChunkPool?
Date Fri, 25 Mar 2016 16:58:25 GMT

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

Elliott Clark commented on HBASE-14613:

bq.Jingcheng, pointed this JIRA to me. I am kind of curious, have you guys tried to tune G1GC
for that "significant amount of memory basically pinned in old gen forever" case?

Always have this on.

Setting it lower doesn't help since this is all about the promotion from young to old an g1
preferring not to do mixed. But we tried it.

Setting this higher helped a lot but we have enough happening on these boxes that it started
to hurt performance.

Setting this lower just moved what caused the long gc's.

> 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

View raw message