[
https://issues.apache.org/jira/browse/HBASE-15555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15216539#comment-15216539
]
stack commented on HBASE-15555:
-------------------------------
bq. Do you want to raise a JIRA for this? I think the subtasks here would cover
it.
The phenomeon is disturbing, that though we are creating less garbage, it makes
no difference time-wise when GC'ing. Worth monitoring as an independent concern
I'd say... as subtask?
And similar the issue of SLABs vs G1GC... Need to get over that hurdle too...
definitively... Get to the bottom of it.
> 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. Collect it all in one place so we are
> aligned rather than each trying to do it for themselves.
> 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)
