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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/01/30 12:36:08 UTC

[jira] [Commented] (OAK-1366) Implement DocumentNodeState.getChildNodeCount(long)

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

Michael Dürig commented on OAK-1366:
------------------------------------

This greatly improves the scenario described [previously | https://issues.apache.org/jira/browse/OAK-1361?focusedCommentId=13885457&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13885457]. But only if I increase the cache settings (memoryCacheSize = 1G). Otherwise I still see a bottleneck on {{getChildNodeCount}} doing round trips to the server. 

> Implement DocumentNodeState.getChildNodeCount(long)
> ---------------------------------------------------
>
>                 Key: OAK-1366
>                 URL: https://issues.apache.org/jira/browse/OAK-1366
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 0.16
>
>
> Without this implementation the call will go to AbstractNodeState and retrieve up to 100 child nodes (using DocumentNodeState) even if less are requested.
> See also Michaels comment in OAK-1361.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)