[
https://issues.apache.org/jira/browse/OAK-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688010#comment-13688010
]
Michael Dürig edited comment on OAK-877 at 6/19/13 1:59 PM:
------------------------------------------------------------
These graphs show how long it takes to deliver the observation events generated
from 1000 added nodes. The vertical axis shows the number of pending events at
a given time. The horizontal axis shows the time elapsed in milliseconds.
In "1 transaction" all nodes are persisted with a single save call whereas in
"10 transaction" the nodes are persisted with a total of 10 intermediate save
calls.
The raw data is here:
https://docs.google.com/spreadsheet/pub?key=0AqWOLyLNdfKedDk4a01OSU5mUmxNT1BVRERGcTdBUkE&output=html
was (Author: mduerig):
These graphs show how long it takes to deliver the observation events
generated from 1000 added nodes. The vertical axis shows the number of pending
events at a given time. The horizontal axis shows the time elapsed in
milliseconds.
In "1 transaction" all nodes are persisted with a single save call whereas in
"10 transaction" the nodes are persisted with a total of 10 intermediate save
calls.
> 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
