[
https://issues.jboss.org/browse/ISPN-2244?page=com.atlassian.jira.plugin....
]
Robert Stupp commented on ISPN-2244:
------------------------------------
OK - I have to dig a bit deeper into the code beside a big project going live in the next
15 days.
Would be nice, if ISPN-2240 is resolved before, because our "standard" load test
raises a huge amount of get/put requests against the same keys concurrently.
I can use our "standard" load test to query some numbers for
storeAsBinary(key=false/true,value=false/true,transparent=false/true) ;-)
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