[
https://issues.apache.org/jira/browse/OAK-2829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Egli updated OAK-2829:
-----------------------------
Attachment: OAK-2829-improved-doc-cache-invaliation.patch
Attached [^OAK-2829-improved-doc-cache-invaliation.patch] which is a suggestion
on how to avoid invalidating the entire document cache when doing a
{{backgroundRead}} but instead making use of the new journal: ie only
invalidate from the document cache what has actually changed.
I'd like to get an opinion ([~mreutegg], [~chetanm]?) on this first, I have a
load test pending locally which found invalidation of the document cache to be
the slowest part thus wanted to optimize this first.
Open still/next:
* also invalidate only necessary parts from the docChildrenCache
* junits for all of these
> Comparing node states for external changes is too slow
> ------------------------------------------------------
>
> Key: OAK-2829
> URL: https://issues.apache.org/jira/browse/OAK-2829
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Blocker
> Labels: scalability
> Fix For: 1.3.1, 1.2.3
>
> Attachments: CompareAgainstBaseStateTest.java, OAK-2829-gc-bug.patch,
> OAK-2829-improved-doc-cache-invaliation.patch, graph-1.png, graph.png
>
>
> Comparing node states for local changes has been improved already with
> OAK-2669. But in a clustered setup generating events for external changes
> cannot make use of the introduced cache and is therefore slower. This can
> result in a growing observation queue, eventually reaching the configured
> limit. See also OAK-2683.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
