[
https://issues.apache.org/jira/browse/OAK-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574239#comment-15574239
]
Chetan Mehrotra commented on OAK-3036:
--------------------------------------
Marking this as blocker for next release to ensure that it gets resolved or we
come to some conclusion on what needs to be done here
> DocumentRootBuilder: revisit update.limit default
> -------------------------------------------------
>
> Key: OAK-3036
> URL: https://issues.apache.org/jira/browse/OAK-3036
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mongomk, rdbmk
> Reporter: Julian Reschke
> Priority: Blocker
> Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4,
> performance
> Fix For: 1.6, 1.5.13
>
>
> 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)
