[jira] [Commented] (OAK-3494) MemoryDiffCache should also check parent paths before falling to Loader (or returning null)

["Vikas Saurabh (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15033912#comment-15033912 ] 

Vikas Saurabh commented on OAK-3494:
------------------------------------

[~mreutegg], I think we should backport this issue as it's useful with journal optimization.

> MemoryDiffCache should also check parent paths before falling to Loader (or returning null)
> -------------------------------------------------------------------------------------------
>
>                 Key: OAK-3494
>                 URL: https://issues.apache.org/jira/browse/OAK-3494
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Vikas Saurabh
>            Assignee: Marcel Reutegger
>              Labels: candidate_oak_1_0, candidate_oak_1_2, performance
>             Fix For: 1.3.10
>
>         Attachments: OAK-3494-1.patch, OAK-3494-2.patch, OAK-3494-TestCase.patch, OAK-3494.patch
>
>
> Each entry in {{MemoryDiffCache}} is keyed with {{(path, fromRev, toRev)}} for the list of modified children at {{path}}. A diff calcualted by {{DocumentNodeStore.diffImpl}} at '/' (passively via loader) or {{JournalEntry.applyTo}} (actively) fill each path for which there are modified children (including the hierarchy)
> But, if an observer calls {{compareWithBaseState}} on a unmodified sub-tree, the observer will still go down to {{diffImpl}} although cached parent entry can be used to answer the query.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)