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-14942) Allow turning off BoundedByteBufferPool
Date Mon, 07 Dec 2015 23:05:10 GMT

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

Elliott Clark commented on HBASE-14942:

bq.So this ain't in the old gen?
Other way around. This is getting in the old gen when G1 does better with things not in the
old gen. Since the G1 is a copying collector there's no need to try and keep from fragmenting
the heap. That's already taken care of. Also since the g1 will decide how big your young gen
needs to be, there's a detriment to retain things just to keep from having more data in the

> Allow turning off BoundedByteBufferPool
> ---------------------------------------
>                 Key: HBASE-14942
>                 URL: https://issues.apache.org/jira/browse/HBASE-14942
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.2.0, 1.3.0
>            Reporter: Elliott Clark
>            Assignee: Elliott Clark
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>         Attachments: HBASE-14942.patch
> The G1 does a great job of compacting, there's no reason to use the BoundedByteBufferPool
when the JVM can it for us. So we should allow turning this off for people who are running
new jvm's where the G1 is working well.

This message was sent by Atlassian JIRA

View raw message