hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gaojinchao (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4970) Allow better control of resource consumption in HTable (backport HBASE-4805 to 0.90 branch)
Date Fri, 09 Dec 2011 09:40:40 GMT

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

gaojinchao commented on HBASE-4970:
-----------------------------------

In HBASE-4970_Branch90_V2.patch  I added a parameter to change keepAliveTime as well.

                
> Allow better control of resource consumption in HTable (backport HBASE-4805 to 0.90 branch)
> -------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4970
>                 URL: https://issues.apache.org/jira/browse/HBASE-4970
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.90.4
>            Reporter: gaojinchao
>            Assignee: gaojinchao
>            Priority: Trivial
>             Fix For: 0.90.5
>
>         Attachments: HBASE-4970_Branch90.patch, HBASE-4970_Branch90_V1_trial.patch, HBASE-4970_Branch90_V2.patch
>
>
> In my cluster, I changed keepAliveTime from 60 s to 3600 s.  Increasing RES is slowed
down.
> Why increasing keepAliveTime of HBase thread pool is slowing down our problem occurance
[RES value increase]?
> You can go through the source of sun.nio.ch.Util. Every thread hold 3 softreference of
direct buffer(mustangsrc) for reusage. The code names the 3 softreferences buffercache. If
the buffer was all occupied or none was suitable in size, and new request comes, new direct
buffer is allocated. After the service, the bigger one replaces the smaller one in buffercache.
The replaced buffer is released.
> So I think we can add a parameter to change keepAliveTime of Htable thread pool.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message