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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2013/03/04 15:59:13 UTC

[jira] [Resolved] (OAK-665) Excessive MK.nodeExists() calls with many child nodes

     [ https://issues.apache.org/jira/browse/OAK-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-665.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 0.7

Fixed in revision: 1452336

The cache in KernelNodeStore now also caches the result of a nodeExists() call, which returned false (node does not exist).
                
> Excessive MK.nodeExists() calls with many child nodes
> -----------------------------------------------------
>
>                 Key: OAK-665
>                 URL: https://issues.apache.org/jira/browse/OAK-665
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 0.6
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>             Fix For: 0.7
>
>
> The number of calls to MK.nodeExists() go up excessively once a node reaches KernelNodeState.MAX_CHILD_NODE_NAMES.
> There are a *lot* of repeated calls to MK.nodeExists() for the same path. E.g. using the test from OAK-643, the nodeExists() call start to spike once MAX_CHILD_NODE_NAMES is reached. Adding another 100 child nodes then resulted in 400 successive calls to "/testRoot/test4/oak:index" and many more calls to other paths.

--
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