You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2016/11/02 11:13:58 UTC

[jira] [Commented] (OAK-3036) DocumentRootBuilder: revisit update.limit default

    [ https://issues.apache.org/jira/browse/OAK-3036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628627#comment-15628627 ] 

Marcel Reutegger commented on OAK-3036:
---------------------------------------

This issue is also related to OAK-4536 and OAK-4503, which showed that a branch was created even when the update.limit was not yet reached. Those two issues are fixed in trunk but I agree it still makes sense to increase update.limit.

> 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
>            Assignee: Chetan Mehrotra
>            Priority: Blocker
>              Labels: candidate_oak_1_0, candidate_oak_1_2, candidate_oak_1_4, performance
>             Fix For: 1.6, 1.5.14
>
>
> 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)