[
https://issues.apache.org/jira/browse/HBASE-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-5056.
--------------------------
Resolution: Later
Closing as later. Reopen if still an issue in recent versions.
> [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: beginner
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
