[infinispan-issues] [JBoss JIRA] (ISPN-1674) Use SingleKeyNonTxInvocationContext where possible

Manik Surtani (Updated) (JIRA) jira-events at lists.jboss.org
Thu Jan 5 11:04:10 EST 2012


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

Manik Surtani updated ISPN-1674:
--------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/785

    
> Use SingleKeyNonTxInvocationContext where possible
> --------------------------------------------------
>
>                 Key: ISPN-1674
>                 URL: https://issues.jboss.org/browse/ISPN-1674
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Core API
>    Affects Versions: 5.1.0.CR2
>            Reporter: Manik Surtani
>            Assignee: Manik Surtani
>            Priority: Minor
>             Fix For: 5.1.0.CR3
>
>
> A CPU and memory performance improvement.  SingleKeyNonTxInvocationContext is used in some cases where we know only a single key is accessed by a command.  But there are other places (evict, putForExternalRead) where a map-like context is still used.

--
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

        


More information about the infinispan-issues mailing list