You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/03/29 07:42:25 UTC
[jira] [Updated] (HBASE-15555) Memory Management
[ https://issues.apache.org/jira/browse/HBASE-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-15555:
--------------------------
Attachment: download.svg
Start of a diagram identifying current bigbuffer allocations.
> 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)