[infinispan-issues] [JBoss JIRA] (ISPN-1542) InvocationContext should not keep entries in an BidirectionalLinkedHashMap

[Manik Surtani (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-1542:
--------------------------------

        Fix Version/s: 5.1.0.BETA5
                       5.1.0.FINAL
    Affects Version/s: 5.0.0.FINAL
          Description: 
At the moment the InvocationContext keeps the looked up entries in an BidirectionalLinkedHashMap. It uses the BidirectionalLinkedHashMap in order to commit the entries in the reversed order in which they were added to the context. This is an inherited feature from JBossCache, where it made sense due to cache's tree structure. It doesn't make sense in Infinispan though, and it adds an unnecessary burden to the InvocationContext. 
The problem is particularly performance costly in the case of non-tx caches, where most of the operations only need a single entry lookup to be held in the invocation context.

  was:
ATM the InvocationContext keeps the looked up entries in an BidirectionalLinkedHashMap. It uses the BidirectionalLinkedHashMap in order to commit the entries in the reversed order in which they were added to the context. This is an inherited feature from JBossCache, where it made sense due to cache's tree structure. It doesn't make sense in Infinispan though, and it adds an unnecessary burden to the InvocationContext. 
The problem is particularly performance costly in the case of non-tx caches, where most of the operations only need a single entry lookup to be held in the invocation context.

           Complexity: Low
          Component/s: Core API

    
> InvocationContext should not keep entries in an BidirectionalLinkedHashMap
> --------------------------------------------------------------------------
>
>                 Key: ISPN-1542
>                 URL: https://issues.jboss.org/browse/ISPN-1542
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core API
>    Affects Versions: 5.0.0.FINAL
>            Reporter: Mircea Markus
>            Assignee: Manik Surtani
>              Labels: optimization
>             Fix For: 5.1.0.BETA5, 5.1.0.FINAL
>
>
> At the moment the InvocationContext keeps the looked up entries in an BidirectionalLinkedHashMap. It uses the BidirectionalLinkedHashMap in order to commit the entries in the reversed order in which they were added to the context. This is an inherited feature from JBossCache, where it made sense due to cache's tree structure. It doesn't make sense in Infinispan though, and it adds an unnecessary burden to the InvocationContext. 
> The problem is particularly performance costly in the case of non-tx caches, where most of the operations only need a single entry lookup to be held in the invocation context.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira