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 2017/02/01 14:03:51 UTC

[jira] [Commented] (OAK-5559) Reduce reads with overlapping previous documents

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

Marcel Reutegger commented on OAK-5559:
---------------------------------------

Added an ignored test to trunk that shows the problem: http://svn.apache.org/r1781248

> Reduce reads with overlapping previous documents
> ------------------------------------------------
>
>                 Key: OAK-5559
>                 URL: https://issues.apache.org/jira/browse/OAK-5559
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, documentmk
>    Affects Versions: 1.6.0
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>              Labels: observation, performance
>             Fix For: 1.8
>
>         Attachments: cost-of-reading-in-past.png
>
>
> Reading a node state in a past revision can become expensive when the change history in the previous documents have overlapping changes. In this case, the changes in the previous documents must be merge sorted to find the correct value for the properties on the node. The more overlapping ranges there are, the more sorting is needed.
> There is a prominent node in the repository that seems to create quite many of those previous documents. The {{/:async}} nodes gets frequent updates and is therefore split on a regular basis. Because the properties on this node are not all updated at the same time, it is quite likely that previous document ranges overlap.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)