hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4956) Control direct memory buffer consumption by HBaseClient
Date Sat, 07 Jan 2012 05:45:39 GMT

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

Lars Hofhansl commented on HBASE-4956:

@Stack and Ted: Yes, if the application uses the API introduced in HBASE-4805 the number of
threads doing network ops is limited to a single thread pools (that can be sized accordingly).

Still not ideal. The regionserver side of things does chunking (8k chunks by default), so
even if a lot of buffers are cached for a lot of threads it won't add to much memory - even
for 1000 threads each caching 3 buffer you'd only use 24mb, and since they are the same size
they are reusable). Maybe the client do the same.

> Control direct memory buffer consumption by HBaseClient
> -------------------------------------------------------
>                 Key: HBASE-4956
>                 URL: https://issues.apache.org/jira/browse/HBASE-4956
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Ted Yu
> As Jonathan explained here https://groups.google.com/group/asynchbase/browse_thread/thread/c45bc7ba788b2357?pli=1
, standard hbase client inadvertently consumes large amount of direct memory.
> We should consider using netty for NIO-related tasks.

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


View raw message