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 "Francesco Mari (JIRA)" <ji...@apache.org> on 2016/07/14 19:58:22 UTC

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

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

Francesco Mari updated OAK-3036:
--------------------------------
    Fix Version/s:     (was: Segment Tar 0.0.4)
                   Segment Tar 0.0.6

> 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, segment-tar
>            Reporter: Julian Reschke
>              Labels: performance
>             Fix For: 1.6, Segment Tar 0.0.6
>
>
> 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)