[
https://issues.apache.org/jira/browse/OAK-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903948#comment-13903948
]
Michael Dürig commented on OAK-1413:
------------------------------------
At http://svn.apache.org/r1569263 I use a more stable method to test for the
expected {{O (n log n)}} behaviour. This method compares the slope of the
measured runtimes against the slope of {{n log n}} (i.e. {{d/dn n log n = 1 +
log n}}) for the respective input sizes {{n}}. The number of values for which
the measured running time does not exceed that bound is used as a test
statistic for a subsequent binomial test. The binomial test uses a significance
level of 5% to decide whether the measured growth is acceptable or whether it
exceeds the expected bound.
With this new method I still see the same test failures for
{{LargeOperationIT#largeCopy}} (OAK-1414), {{LargeOperationIT#largeMove}}
(OAK-1415) and {{LargeOperationIT#manySiblings}} (OAK-1416). In addition I see
a new test failure for {{LargeOperationIT#slowListener}} on the document node
store (OAK-1429). I'll follow up on these issues with the particulars.
> 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 as expected wrt. 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)
