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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2015/07/01 15:16:06 UTC
[jira] [Commented] (OAK-2646) Look for alternative cache
invalidation logic for better performance
[ https://issues.apache.org/jira/browse/OAK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610210#comment-14610210 ]
Vikas Saurabh commented on OAK-2646:
------------------------------------
Since OAK-3002 is now resolved, should we close this?
(cc [~chetanm], [~mreutegg])
> Look for alternative cache invalidation logic for better performance
> --------------------------------------------------------------------
>
> Key: OAK-2646
> URL: https://issues.apache.org/jira/browse/OAK-2646
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Reporter: Chetan Mehrotra
> Labels: performance
> Fix For: 1.3.3
>
>
> Current cache invalidation logic has a higher cost. For e.g. in one of the deployment following log was seen
> {noformat}
> 12.03.2015 09:24:25.579 *INFO* [DocumentNodeStore background thread] org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore Background operations stats (clean:0, split:0, write:0, read:11848 ReadStats{cacheStats:InvalidationResult{invalidationCount=4, upToDateCount=286761, cacheSize=300411, timeTaken=10589, queryCount=654, cacheEntriesProcessedCount=138633}, head:1, cache:11842, dispatch:5, purge:0}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)