[jbosscache-issues] [JBoss JIRA] Updated: (JBCACHE-1471) Slow cache.get for fqn with a large number of key/value entries.
Alex Kluge (JIRA)
jira-events at lists.jboss.org
Wed Jan 28 18:13:44 EST 2009
[ https://jira.jboss.org/jira/browse/JBCACHE-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Kluge updated JBCACHE-1471:
--------------------------------
Attachment: containsKeyDirect.patch
> Slow cache.get for fqn with a large number of key/value entries.
> ----------------------------------------------------------------
>
> Key: JBCACHE-1471
> URL: https://jira.jboss.org/jira/browse/JBCACHE-1471
> Project: JBoss Cache
> Issue Type: Patch
> Security Level: Public(Everyone can see)
> Affects Versions: 3.0.2.GA
> Environment: Encountered when using a TcpDelegatingCacheLoader
> Reporter: Alex Kluge
> Assignee: Manik Surtani
> Priority: Minor
> Attachments: containsKeyDirect.patch
>
>
> Stress tests of JBoss Cache with a far cache, and a large number (10K+) of key/value pairs in a node
> did not perform as well as I would expect. On a read of the cache, cache.get(fqn, key), a large amount
> of time was spent determining whether the data needed to be loaded from the far cache.
> The big time sink is the n. getKeysDirect() call in org.jboss.cache.interceptors.CacheLoaderInterceptor,
> which copies the keyset. As expected, introducing a containsKeyDirect(K key) method to NodeSPI, and
> implementation classes where needed, allowed for a significant speedup when the new method is used
> in place of n.getKeysDirect().contains(key). If this is a reasonable path, I have attached the patch file to this
> issue.
--
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
More information about the jbosscache-issues
mailing list