[infinispan-issues] [JBoss JIRA] (ISPN-2191) Defaultcachemanager.getCache(name) is slow
Galder Zamarreño (JIRA)
jira-events at lists.jboss.org
Tue Aug 14 07:00:14 EDT 2012
[ https://issues.jboss.org/browse/ISPN-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12711411#comment-12711411 ]
Galder Zamarreño commented on ISPN-2191:
----------------------------------------
This is odd, I guess if the cache store appears in the thread dump, it's cos you have preloading enabled.
However, even if preloading is enabled, it should only happen once, when the cache is retrieved first time. Subsequent getCache calls for the same cache name should not show this. Maybe you have multiple caches with preload and the first time you call each is slow?
Try disabling preload and load things lazily.
> Defaultcachemanager.getCache(name) is slow
> ------------------------------------------
>
> Key: ISPN-2191
> URL: https://issues.jboss.org/browse/ISPN-2191
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 5.1.5.FINAL
> Reporter: Dominik Obermaier
> Assignee: Manik Surtani
> Priority: Minor
>
> With the help of JVisualVM I found out, that 63% cpu time of the application was needed in org.infinispan.loaders.file.FileCacheStore.lodaBucket and 25% in org.infinispan.DefaultCacheManager$Cachewrapper.getCache.
> The workaround is to share one instance of the cache for all classes, so a getCache("name) can be avoided.
--
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