jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Sedding (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OAK-3163) Improve binary comparison during repeated upgrades
Date Wed, 29 Jul 2015 12:46:04 GMT

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

Julian Sedding edited comment on OAK-3163 at 7/29/15 12:45 PM:
---------------------------------------------------------------

Attached patch that leverages the content-identity comparison in {{AbstractBlob#equal}}. This
speeds up comparison of binaries and thus the upgrade of repositories with a significant amount
of binaries.

The copy-phase while incrementally upgrading a repository with 2.6mio nodes was 4x faster
with this patch (43min vs 10min).


was (Author: jsedding):
Attached patch that leverages the content-identity comparison in {{AbstractBlob#equal}}. This
speeds up comparison of binaries and thus the upgrade of repositories with a significant amount
of binaries.

> Improve binary comparison during repeated upgrades
> --------------------------------------------------
>
>                 Key: OAK-3163
>                 URL: https://issues.apache.org/jira/browse/OAK-3163
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>    Affects Versions: 1.2.3, 1.3.3
>            Reporter: Julian Sedding
>              Labels: performance
>         Attachments: OAK-3163.patch
>
>
> OAK-2619 introduced the possibility to run the same upgrade repeatedly and achieve incremental
upgrades. This reduces the time taken for {{CommitHook}} processing, because the diff is reduced.
> However, for incremental upgrades to be really useful, the content-copy phase needs to
be fast. Currently an optimization that was proposed in OAK-2626 was lost due to the implementation
of a better solution to some part of the problem. 



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

Mime
View raw message