hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14470) Reduce memory pressure generated by client
Date Thu, 28 Apr 2016 09:12:13 GMT

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

Mikhail Antonov commented on HBASE-14470:
-----------------------------------------

[~stack] [~ndimiduk] - moving out of 1.3.0 due to inactivity. Please feel free to bring it
back in 1.3 if you have bandwidth to work on it.

> 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.4.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)

Mime
View raw message