You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2013/06/13 10:38:20 UTC
[jira] [Updated] (OAK-854) Use weight based caching limit instead
of size based limits
[ https://issues.apache.org/jira/browse/OAK-854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra updated OAK-854:
--------------------------------
Fix Version/s: 0.9
> Use weight based caching limit instead of size based limits
> -----------------------------------------------------------
>
> Key: OAK-854
> URL: https://issues.apache.org/jira/browse/OAK-854
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Affects Versions: 0.8
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Fix For: 0.9
>
>
> Current caching logic in MongoMK for various caches control the cache size on the basis of number of entries. It should be changed to use a Weight based [1] approach where the size of cache is controlled by the amount of memory it takes. Following changes to be done
> # Switch to weight based caching strategy
> # Add suitable logic to compute the *weight* of various cache entries (Node,Document etc).
> # Determine suitable default value for various cache
> # If possible configure the various cache size via single size by allocating the size proportionally
> For #2 we can make use of methods added as part of o.a.j.mongomk.MeasureMemory
> [1] http://code.google.com/p/guava-libraries/wiki/CachesExplained#Size-based_Eviction
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira