[
https://issues.apache.org/jira/browse/OAK-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605393#comment-14605393
]
Michael Dürig commented on OAK-3036:
------------------------------------
+1 this should also be beneficial for the SegmentMK.
OTHO we should try to think for a deeper fix. It would be better to persist
transient changes "when required" instead of on a fixed number of updates. E.g.
when heap gets scarce.
> DocumentRootBuilder: revisit update.limit default
> -------------------------------------------------
>
> Key: OAK-3036
> URL: https://issues.apache.org/jira/browse/OAK-3036
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: mongomk, rdbmk
> Reporter: Julian Reschke
>
> update.limit decides whether a commit is persisted using a branch or not. The
> default is 10000 (and can be overridden using the system property).
> A typical call pattern in JCR is to persist batches of ~1024 nodes. These
> translate to more than 10000 changes (see PackageImportIT), due to JCR
> properties, and also indexing commit hooks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
