[infinispan-issues] [JBoss JIRA] (ISPN-2244) Transparently hold serialized representations of keys and values
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Sep 4 09:44:32 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715751#comment-12715751 ]
Galder Zamarreño commented on ISPN-2244:
----------------------------------------
Indeed. Fancy contributing a patch for this? ;)
That'd get you the snapshot that you're after and you'd be able to compare and provide us with some numbers :)
Here's our [contribution guide|https://docs.jboss.org/author/x/ZABG] in case you're interested.
> Transparently hold serialized representations of keys and values
> ----------------------------------------------------------------
>
> Key: ISPN-2244
> URL: https://issues.jboss.org/browse/ISPN-2244
> Project: Infinispan
> Issue Type: Enhancement
> Reporter: Robert Stupp
> Assignee: Mircea Markus
>
> Serialization/deserialization might become very expensive when working with cached large java objects that are created and used on many different nodes.
> At the moment, the setting storeAsBinary() allows you to "die" either one:
> * serialize/deserialize when the cache is accessed
> * serialize/deserialize when L1 is filled or invalidated, object fetched from other node, object is replicated on put
> It might be a good solution to add a third mode:
> * At a put() operation, the Java object is put into the cache
> * When the serialized representation is required first, it is created from the Java object (or during the put() operation)
> * The serialized representation is reused every time when needed.
> Means: cache the serialized representation of keys and values.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list