You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/09/23 20:48:04 UTC

[jira] [Resolved] (HBASE-14470) Reduce memory pressure generated by client

     [ https://issues.apache.org/jira/browse/HBASE-14470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-14470.
---------------------------
       Resolution: Fixed
         Assignee: stack
    Fix Version/s: 1.3.0
                   1.2.0
                   2.0.0

Pushed small patch to tests only to branch-1.2+

> Reduce memory pressure generated by client
> ------------------------------------------
>
>                 Key: HBASE-14470
>                 URL: https://issues.apache.org/jira/browse/HBASE-14470
>             Project: HBase
>          Issue Type: Task
>          Components: Client, Performance
>    Affects Versions: 1.3.0
>            Reporter: Nick Dimiduk
>            Assignee: stack
>             Fix For: 2.0.0, 1.2.0, 1.3.0
>
>         Attachments: allocation-by-class.jpg, allocation-by-thread.jpg, c+ma.jfc, object-stats.jpg
>
>
> I think there's room for improvement in our client's memory profile. I ran ltt with jfr running, attaching some snaps of what my client sees. Looks like some kind of object pool or block encoding for result objects will give us a lot of bang for the buck re: allocations and GC pressure. We probably also want to look for an alternative way to represent result objects, something besides the java Map interface with it's Entry bloat.



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