[
https://issues.apache.org/jira/browse/OAK-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897966#comment-13897966
]
Michael Dürig commented on OAK-1413:
------------------------------------
{{org.apache.jackrabbit.oak.jcr.LargeOperationIT#largeCopy}} is fine for
segment but does not scale linearly with the number of copied nodes in the case
of document:
{code}
seq quotients: 0.3405705938810861, 0.6213776455397744, 1.0301212438790814,
1.0087703911594457, 1.0535559033211614
doc quotients: 1.1803765754650501, 0.33168970806199227, 0.8160753821577706,
1.4619226777374157, 1.9342440796702938
{code}
Note how in the case of the document node store copying trees with 32768 and
with 131072 nodes each took super linearly longer than copying the respective
previous amount of nodes.
> 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)
