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 "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/02/19 10:57:14 UTC
[jira] [Commented] (OAK-638) Avoid branch/merge for small commits
[ https://issues.apache.org/jira/browse/OAK-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581171#comment-13581171 ]
Jukka Zitting commented on OAK-638:
-----------------------------------
With the SegmentMK this is a non-issue, as it automatically buffers small commits in memory.
> Avoid branch/merge for small commits
> ------------------------------------
>
> Key: OAK-638
> URL: https://issues.apache.org/jira/browse/OAK-638
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Marcel Reutegger
> Priority: Minor
>
> The branch/merge features on the MicroKernel were initially introduced to stage changes of large commits. Currently oak-core creates a branch even for small changes like updating a property. I think this introduces quite some overhead for scenarios with highly concurrent updates. E.g. think of a twitter like application or a forum with comments. Well, basically user generated content. These update tend to be rather small (couple of nodes) but frequent and concurrent.
> Right now oak-core always does:
> - MK.branch()
> - MK.commit() to branch
> - MK.merge()
> For small commits, it ideally should do:
> - MK.commit() to trunk
--
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