You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Amit Jain (JIRA)" <ji...@apache.org> on 2014/09/30 09:42:43 UTC
[jira] [Updated] (OAK-1414) Copying a large subtrees does not scale
as expected in the number of copied nodes on document node stores
[ https://issues.apache.org/jira/browse/OAK-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amit Jain updated OAK-1414:
---------------------------
Fix Version/s: (was: 1.1)
1.1.0
> Copying a large subtrees does not scale as expected in the number of copied nodes on document node stores
> ---------------------------------------------------------------------------------------------------------
>
> Key: OAK-1414
> URL: https://issues.apache.org/jira/browse/OAK-1414
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Michael Dürig
> Assignee: Michael Dürig
> Fix For: 1.1.0
>
>
> {{org.apache.jackrabbit.oak.jcr.LargeOperationIT#largeCopy}} does not scale linearly with the number of copied nodes in the case of document:
> {code}
> quotients: 1.1803765754650501, 0.33168970806199227, 0.8160753821577706, 1.4619226777374157, 1.9342440796702938
> {code}
> Note how copying trees with 32768 and with 131072 nodes each took super linearly longer than copying the respective previous amount of nodes. See also OAK-1413 on how to read these numbers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)