[
https://issues.apache.org/jira/browse/OAK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14570538#comment-14570538
]
Julian Reschke commented on OAK-2646:
-------------------------------------
a) Yes.
b) No, it's not hierarchy-aware, mainly for two reasons: 1) building the
hierarchy information can be memory-intensive, 2) there's a layer violation
here; the DocumentStore API is currently agnostic about what goes into an ID
(we can change that, but we should do that properly)
> 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.0
>
>
> 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)
