[jbosscache-issues] [JBoss JIRA] Commented: (JBCACHE-1082) Optimise nodes for single elements

[Manik Surtani (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCACHE-1082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12434288#action_12434288 ] 

Manik Surtani commented on JBCACHE-1082:
----------------------------------------

Ok, the SingletonMap approach has made things much quicker for writers, due to faster copy-on-write (needed by MVCC) when compared to using a real Map for data.  And the memory overhead is much better too.

> 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: Manik Surtani
>             Fix For: 3.0.0.GA
>
>         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