[
https://issues.apache.org/jira/browse/OAK-2969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dürig updated OAK-2969:
-------------------------------
Component/s: (was: core)
mongomk
> Reduce DocumentStore UpdateOp memory footprint
> ----------------------------------------------
>
> Key: OAK-2969
> URL: https://issues.apache.org/jira/browse/OAK-2969
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk
> Affects Versions: 1.2.2
> Reporter: Timothee Maret
>
> As described in [0] large commits consume a fair amount of memory. With very
> large commits, this become problematic as commits may eat up 100GB or more
> and thus causing OOME and aborting the commit.
> For instances using the DocumentStore and for cases where the tree is deep
> but not sparse, some of the HashMaps in
> {code}
> org.apache.jackrabbit.oak.plugins.document.UpdateOp
> {code}
> actually contain less entries than their capacity (built with default
> capacity).
> This issue covers a simple way to reduce the memory consumption in this case
> by simply creating HashMaps of the required capacity (where applicable) or of
> minimal capacity (1) where unknown.
> [0] http://permalink.gmane.org/gmane.comp.apache.jackrabbit.oak.devel/8196
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
