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] [Resolved] (OAK-8489) Reduce memory usage of in-memory commit
Date Tue, 23 Jul 2019 13:05:00 GMT

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

Marcel Reutegger resolved OAK-8489.
       Resolution: Fixed
    Fix Version/s: 1.16.0

Committed to trunk: http://svn.apache.org/r1863640

> Reduce memory usage of in-memory commit
> ---------------------------------------
>                 Key: OAK-8489
>                 URL: https://issues.apache.org/jira/browse/OAK-8489
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.16.0
> The memory usage of an in-memory commit currently depends on the number of modified nodes
and the structure of modified documents. The first is limited by the updateLimit on the DocumentNodeStateBuilder.
When the updateLimit is reached, the changes are pushed to a branch. The structure of the
modified documents comes into play, when those documents have a rather high memory usage.
The current commit implementation performs the update in a single call to {{DocumentStore.createOrUpdate()}},
which has a return type of {{List<Document>}}. The returned list contains the documents
as they looked before the update. With a default of 100'000 as the updateLimit and heavy weight
modified Documents, this can result in a high memory usage.

This message was sent by Atlassian JIRA

View raw message