[JBoss JIRA] Created: (JBCACHE-1411) Marshaller has no special treatment of arrays, even arrays of primitives or known types
by Manik Surtani (JIRA)
Marshaller has no special treatment of arrays, even arrays of primitives or known types
---------------------------------------------------------------------------------------
Key: JBCACHE-1411
URL: https://jira.jboss.org/jira/browse/JBCACHE-1411
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Replication
Affects Versions: 3.0.0.BETA1, 2.2.0.GA
Reporter: Manik Surtani
Assignee: Manik Surtani
Fix For: 3.0.0.GA
This is an inefficiency that causes, for example, the marshalling of a byte[] to fall back to Serializable. E.g., cache.put(fqn, key, new byte[]{1, 2, 3, 4}) would result in the byte[] being serialized as a Serializable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Resolved: (JBCACHE-1368) Optimize the CacheLoader.putAll() method so reads are not necessary
by Manik Surtani (JIRA)
[ https://jira.jboss.org/jira/browse/JBCACHE-1368?page=com.atlassian.jira.p... ]
Manik Surtani resolved JBCACHE-1368.
------------------------------------
Fix Version/s: 3.0.0.CR1
Resolution: Done
> Optimize the CacheLoader.putAll() method so reads are not necessary
> -------------------------------------------------------------------
>
> Key: JBCACHE-1368
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1368
> Project: JBoss Cache
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Elias Ross
> Assignee: Manik Surtani
> Fix For: 3.0.0.CR1, 3.0.0.GA
>
>
> Almost all CacheLoader implementations do a read of the existing data map when "putAll" is called but this may be unnecessary as the Cache likely has loaded the cache loader data at some point.
> Manik suggests: "[We] need to analyse in the interceptors and see if that can be done away with. No real reason to do a read here. From the cache loader javadoc for the put(Fqn, Map) method:
> 'Puts all entries of the map into the existing map of the given node, overwriting existing keys, but not clearing the existing map before insertion. '
> "
> One improvement would be to check in the CacheLoader impl. if the Node was already loaded, then the Map merge can happen without the read. However, this logic might better belong in the cache loader interceptor. It might work okay to do this check in the base class for existing CacheLoader impl. as well.
> Relates all JBCACHE-1221 - JDBC cache loader optimization.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months
[JBoss JIRA] Updated: (JBCACHE-1082) Optimise nodes for single elements
by Manik Surtani (JIRA)
[ https://jira.jboss.org/jira/browse/JBCACHE-1082?page=com.atlassian.jira.p... ]
Manik Surtani updated JBCACHE-1082:
-----------------------------------
Fix Version/s: 3.1.0
(was: 3.0.0.GA)
> Optimise nodes for single elements
> ----------------------------------
>
> Key: JBCACHE-1082
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1082
> Project: JBoss Cache
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 2.0.0.CR1
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Fix For: 3.1.0
>
> Attachments: ReplicatedPojoPerfTest.java, UnversionedNode.patch.txt
>
>
> Many use cases just place a single object in a Node. Rather than going through the memory and performance penalties of using Maps for a single entry, we should:
> 1) Create a reference to 2 Objects for key and value, as well as a Map.
> 2) Only initialise/construct the Map if Node.putAll() is called, or when Node.put() is called with a second key/value pair
> 3) Otherwise just hold the key/value pair as direct object refs.
> Would affect UnversionedNode and WorkspaceNodeImpl.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 3 months