[infinispan-issues] [JBoss JIRA] (ISPN-1417) Inefficient and unnecessary clearing of looked up entries when a context is reset
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Wed Apr 25 08:42:24 EDT 2012
[ https://issues.jboss.org/browse/ISPN-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-1417:
--------------------------------
Fix Version/s: (was: 5.0.2.FINAL)
Git Pull Request: https://github.com/infinispan/infinispan/pull/543 (was: https://github.com/infinispan/infinispan/pull/543)
Forum Reference: http://community.jboss.org/thread/172440?tstart=0, http://community.jboss.org/message/626964#626964 (was: http://community.jboss.org/thread/172440?tstart=0, http://community.jboss.org/message/626964#626964)
> Inefficient and unnecessary clearing of looked up entries when a context is reset
> ---------------------------------------------------------------------------------
>
> Key: ISPN-1417
> URL: https://issues.jboss.org/browse/ISPN-1417
> Project: Infinispan
> Issue Type: Bug
> Components: Core API
> Affects Versions: 5.0.1.FINAL
> Reporter: Manik Surtani
> Assignee: Manik Surtani
> Fix For: 5.1.0.BETA1, 5.1.0.FINAL
>
>
> When a context is reset, some implementations call clear() on the looked up entries map. This can be inefficient in microbenchmarks if a large number of entries have been looked up. Contexts should simply nullify looked up entries and let the collection be gc'd.
--
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