jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-535) MergeCommand reads complete tree into memory
Date Mon, 14 Jan 2013 10:54:13 GMT

     [ https://issues.apache.org/jira/browse/OAK-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger updated OAK-535:

    Attachment: OAK-535.patch

This is a work-in-progress patch, which shows what kind of optimization I have in mind.

MergeCommand checks if there were any commits to head in the meantime. If there are none,
then the branch commits are aggregated into a single one and commit to head.

Unfortunately I see some unexpected behaviour in some cases when multiple commits are aggregated.
E.g. see additional test movesInBranch() in MongoMKBranchMergeTest.
> MergeCommand reads complete tree into memory
> --------------------------------------------
>                 Key: OAK-535
>                 URL: https://issues.apache.org/jira/browse/OAK-535
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: mongomk
>    Affects Versions: 0.5
>            Reporter: Marcel Reutegger
>         Attachments: mergefixattempt.patch, OAK-535.patch
> Merging commits to a branch back to head in MongoMK calls MergeCommand, which reads the
complete tree into memory. The more content is in the repository, the longer it takes to store
even a simple update as a property change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message