Improve efficiency of RegionManagerImpl.getRegion ------------------------------------------------- Key: JBCACHE-1536 URL: https://jira.jboss.org/jira/browse/JBCACHE-1536 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Eviction Reporter: Brian Stansberry Assignee: Brian Stansberry A profiling run showed almost 37 ms for 22 invocations. Fqns were /SFSB/container-name/bucketInt/sessionId Region names were /SFSBcontainer-name The trick in JBC 1.x (I believe by genman) of tracking the max length of registered regions and starting searches at that depth should be restored. The lookups also do this: if (regionsRegistry.containsKey(fqnToUse)) { Region r = regionsRegistry.get(fqnToUse); which means 2 searches per request. -- 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