jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Marth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-3018) Use batch-update in backgroundWrite
Date Mon, 24 Aug 2015 12:44:49 GMT

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

Michael Marth updated OAK-3018:
    Fix Version/s:     (was: 1.3.5)

> Use batch-update in backgroundWrite
> -----------------------------------
>                 Key: OAK-3018
>                 URL: https://issues.apache.org/jira/browse/OAK-3018
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Stefan Egli
>              Labels: performance
>             Fix For: 1.3.7
> (From an earlier [post on the list|http://markmail.org/thread/mkrvhkfabit4osli]) The
DocumentNodeStore.backgroundWrite goes through the heavy work of updating the lastRev for
all pending changes and does so in a hierarchical-depth-first manner. Unfortunately, if the
pending changes all come from separate commits (as does not sound so unlikely), the updates
are sent in individual update calls to mongo (whenever the lastRev differs). Which, if there
are many changes, results in many calls to mongo.
> OAK-2066 is about extending the DocumentStore API with a batch-update method. That one,
once available, should thus be used in the {{backgroundWrite}} as well.

This message was sent by Atlassian JIRA

View raw message