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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/04/03 16:27:15 UTC

[jira] [Commented] (OAK-743) Increase default RootImpl.PURGE_LIMIT

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

Michael Dürig commented on OAK-743:
-----------------------------------

+1 for increasing that value. However, let's introduce some kind of feature flag such that we can leave (or set) it to a lower value for the tests. I'd really like to keep it at a low value for running our tests since in the past this caught quite a few regressions.
                
> Increase default RootImpl.PURGE_LIMIT
> -------------------------------------
>
>                 Key: OAK-743
>                 URL: https://issues.apache.org/jira/browse/OAK-743
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> The current default value is 100 modifications until changes are persisted into the branch. I'd like to increase this value to a more reasonable default. 100 modifications are quickly reached, since even a simple setProperty will increment the count. In most cases this means transient modifications are stored into the branch already for a low double digit number of nodes. This adds quite some overhead when the changes set on the higher JCR level is bigger.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira