jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-1416) Adding many siblings does not scale as expected in the number of added nodes
Date Tue, 18 Mar 2014 14:25:44 GMT

    [ https://issues.apache.org/jira/browse/OAK-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13939264#comment-13939264
] 

Michael Dürig commented on OAK-1416:
------------------------------------

Agreed, the description is outdated/incorrect. The test adds a certain number of sibling nodes
and checks that this operation scales O(n log n) in the number of nodes n. I still think this
is a valid expectation though. However, for Mongo there might be a bias introduces at the
point where the number of changes do not fit into the transient space any more. The test does
currently not account for that. Maybe we could run the test with {{-Dupdate.limit=0}} to make
up for this? I'll give it a try. 

> 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)

Mime
View raw message