hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15555) Memory Management
Date Tue, 29 Mar 2016 13:35:25 GMT

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

stack commented on HBASE-15555:
-------------------------------

bq. we use BBs from the pool (BoundedByteBufferPool) and read req into it. 

Like 14490 [RpcServer] reuse request read buffer. Lives lifetime of request does? Why do you
think this is? We are only using the pool? We are reading direct BB -- the socket -- to DBB
from the pool? Would be interesting to find what is going on here.

> Memory Management
> -----------------
>
>                 Key: HBASE-15555
>                 URL: https://issues.apache.org/jira/browse/HBASE-15555
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: stack
>         Attachments: download.svg
>
>
> Umbrella issue on memory management. One-stop shop to learn how we're doing it, tenets,
and work to be done
> Subtasks include:
> + Map of memory allocation and recycling landscape
> + Where are we allocating when we could be recycling
> + MSLAB and G1GC don't go together?
> + Enable MSLAB pool always?
> + With offheap allocations, less GC but it runs for longer?
> + Better heuristics recycling: e.g. HBASE-15525 OutOfMemory could occur when using BoundedByteBufferPool
during RPC bursts
> + See if can do DFSClient buffer reuse: HBASE-15506 FSDataOutputStream.write() allocates
new byte buffer on each operation
> What else?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message