You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Zhihong Yu (Commented) (JIRA)" <ji...@apache.org> on 2011/12/16 20:56:30 UTC

[jira] [Commented] (HBASE-5056) [performance] On upload, 4% of memory allocations are NullInstance

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

Zhihong Yu commented on HBASE-5056:
-----------------------------------

+1 on proposed change.
                
> [performance] On upload, 4% of memory allocations are NullInstance
> ------------------------------------------------------------------
>
>                 Key: HBASE-5056
>                 URL: https://issues.apache.org/jira/browse/HBASE-5056
>             Project: HBase
>          Issue Type: Improvement
>          Components: performance
>            Reporter: stack
>              Labels: noob
>         Attachments: NullInstanceHotSpotMemAllocation.html
>
>
> Profiling a PE upload, I see that 4% of memory allocations are instances of NullInstance (caveat profiler's give distorted view of running app as does PE when it comes to real-world workloads).  See attached profiler output.  Looks like we could save a bunch on object creation if we had our own WritableFactories instance that treated stuff like NullInstance special creating a Singleton NullInstance per declared class type returning these instead of creating new ones.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira