[
https://issues.apache.org/jira/browse/OAK-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897972#comment-13897972
]
Michael Dürig commented on OAK-1413:
------------------------------------
{{org.apache.jackrabbit.oak.jcr.LargeOperationIT#manySiblings}} does not scale
linearly. Neither on a segment nor on a document node store:
{code}
seg quotients: 0.4181951174217804, 0.4163634468727202, 0.8406068389090829,
1.0735629207664423, 1.290574274619522
doc quotients: 1.5713552072927073, 0.6562667320967186, 0.6101785222342979,
2.0164792911151244, 1.6989089236000476
{code}
In both cases adding sibling becomes more expensive when there are already many
siblings. Although the behaviour is more expressed on a document node store.
> 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)
