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 2015/08/24 16:37:46 UTC

[jira] [Commented] (OAK-3259) Optimize NodeDocument.getNewestRevision()

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

Marcel Reutegger commented on OAK-3259:
---------------------------------------

Added a cluster test: http://svn.apache.org/r1697410

> Optimize NodeDocument.getNewestRevision()
> -----------------------------------------
>
>                 Key: OAK-3259
>                 URL: https://issues.apache.org/jira/browse/OAK-3259
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>              Labels: performance
>             Fix For: 1.3.5
>
>
> Most of the time NodeDocument.getNewestRevision() is able to quickly identify the newest revision, but sometimes the code falls to a more expensive calculation, which attempts to read through available {{_revisions}} and {{_commitRoot}} entries. If either of those maps are empty, the method will go through the entire revision history.



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