geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xiaojian zhou (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-6428) PdxInstanceFactory could be optimized to use less memory
Date Tue, 19 Feb 2019 21:57:00 GMT

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

xiaojian zhou commented on GEODE-6428:
--------------------------------------

The following types of objects that wrapped the byte array. We can get rid of them to save
another 100 bytes:
HeapByteBuffer, PdxInputStream, ByteBufferByteSource

> PdxInstanceFactory could be optimized to use less memory
> --------------------------------------------------------
>
>                 Key: GEODE-6428
>                 URL: https://issues.apache.org/jira/browse/GEODE-6428
>             Project: Geode
>          Issue Type: Improvement
>          Components: serialization
>            Reporter: Darrel Schneider
>            Priority: Major
>
> https://issues.apache.org/jira/browse/GEODE-6414 was able to reduce the amount of memory
consumed by the PdxInstance. Further optimizations can be done by getting rid of some of the
extra objects that wrap the byte array owned by the PdxInstance. If the factory is creating
an instance that will never deserialize then optimizing the memory usage of the PdxInstance
is more likely to be of value.
> It seems like an alternative implementation to PdxInstanceImpl could be a class that
just has a byte[] reference, an PdxType reference, and an "int" for the hashCode. For some
operations you might need to use this information to create a full fledged PdxInstanceImpl
at runtime but having the one with the smaller footprint could save around 100 bytes per PdxInstance.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message