[
https://issues.apache.org/jira/browse/OAK-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898004#comment-13898004
]
Michael Dürig commented on OAK-1413:
------------------------------------
{{org.apache.jackrabbit.oak.jcr.LargeOperationIT#largeNumberOfPendingEvents}}
does not scale linearly. Neither on a segment nor on a document node store.
This test asserts that the number of pending observation events (e.g. due to a
large commit or cluster sync) has a linear processing time. That is the time it
takes to process one such event is independent of the total number of events.
{code}
seg quotients: 0.24215928530697586, 0.4065934065934066, 1.7548262548262548,
0.6892189218921893, 1.2083000798084598
doc quotients: 0.2990824434780629, 0.14113885505481122, 0.587378640776699,
1.3122130394857667, 142.65850244926523
{code}
While in the case of the segment node store the numbers do not seem too
worrisome, the document node store seems to start lagging behind badly as soon
as there are more than 32768 pending events.
> Add scalability tests for large operations
> ------------------------------------------
>
> Key: OAK-1413
> URL: https://issues.apache.org/jira/browse/OAK-1413
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: jcr
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 0.17
>
>
> We should add tests asserting large operation scale linearly in the order of
> the size of the operation. Candidates are:
> * large commit
> * move/copy of large tree
> * many siblings
> * large number of pending observation events
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
