[
https://issues.apache.org/jira/browse/OAK-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688039#comment-13688039
]
Jukka Zitting commented on OAK-877:
-----------------------------------
bq. detecting sequences of subsequent local commits
Doing so loses at least the timestamps and potentially other local information
associated with events. Going down that path feels like undoing OAK-775.
In general a full diff over a commit should take just a small fraction of the
time it takes to commit those changes in the first place, and any number of
observers can do such diffs concurrently. And most typical observers are only
interested in a specific subtree, so won't need to do full diffs of all
changes. Thus instead of changing the way commits are reported, I'd just look
at how to optimize away any bottlenecks in event delivery (like the fact that
subtree restrictions are currently not taken advantage of).
> Generating observation events takes too long when intermediate save calls are
> involved
> --------------------------------------------------------------------------------------
>
> Key: OAK-877
> URL: https://issues.apache.org/jira/browse/OAK-877
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Michael Dürig
> Attachments: 1_save.png, 2.save.png
>
>
> Creating observation events is much more expensive when a transaction is
> broken down through intermediate save calls compared to only having a single
> save call.
--
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
