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

Chetan Mehrotra commented on OAK-2626:
--------------------------------------

[~jsedding] Can you have a look at OAK-2882. We also saw slowness caused due to 
frequent access to FileSystem in migration. Given actual migration process does 
not touch the binary content we can speed up (for repeated trials) the 
migration by caching the length information.

With that patch we might not need changes proposed in this patch. So do have a 
look

> Optimize binary comparison for merge during upgrade 
> ----------------------------------------------------
>
>                 Key: OAK-2626
>                 URL: https://issues.apache.org/jira/browse/OAK-2626
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: upgrade
>    Affects Versions: 1.1.7
>            Reporter: Julian Sedding
>            Priority: Minor
>         Attachments: OAK-2626.patch, incremental-upgrade-no-changes.png
>
>
> In OAK-2619 I propose to support repeated upgrades into the same NodeStore.
> This issue does not optimizate the first run, but any subsequent run benefits 
> from the proposed changes.
> One use-case for this feature is to import all content several days before 
> the upgrade and then copy only the delta on the day of the upgrade.
> Assuming that both the source and target repositories use the same 
> FileDataStore, binaries could be efficiently compared by their references.



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

Reply via email to