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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2014/03/18 15:11:44 UTC
[jira] [Commented] (OAK-1416) Adding many siblings does not scale
as expected in the number of added nodes
[ https://issues.apache.org/jira/browse/OAK-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939244#comment-13939244 ]
Marcel Reutegger commented on OAK-1416:
---------------------------------------
I suspect the test fails with the document node store because of the size of the save call. The cost increases significantly when the change set does not fit into memory and the document node store has to reload the nodes from storage again for the commit editors to process them.
>From the description:
bq. adding sibling becomes more expensive when there are already many siblings
I think this is a bit confusing. AFAICS there are no existing siblings in the test and the time is measured to create them all.
> Adding many siblings does not scale as expected in the number of added nodes
> ----------------------------------------------------------------------------
>
> Key: OAK-1416
> URL: https://issues.apache.org/jira/browse/OAK-1416
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
> Reporter: Michael Dürig
> Assignee: Marcel Reutegger
> Priority: Critical
> Fix For: 0.20
>
>
> {{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. See also OAK-1413 on how to read these numbers.
--
This message was sent by Atlassian JIRA
(v6.2#6252)