[
https://issues.apache.org/jira/browse/OAK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044676#comment-14044676
]
Jukka Zitting commented on OAK-656:
-----------------------------------
bq. if Oak cannot efficiently deal with 20+ children it seems like its giving
up on a large number of use cases
The performance degradation with many orderable child nodes is roughly similar
to what you see in Jackrabbit 2.x, so you should be able to go up to thousands
of child nodes before starting to see significant slowdown. Without
orderability you can go up to millions.
> Large number of child nodes not working well with orderable node types
> ----------------------------------------------------------------------
>
> Key: OAK-656
> URL: https://issues.apache.org/jira/browse/OAK-656
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Thomas Mueller
> Priority: Minor
>
> When adding many child nodes to an orderable node, oak gets slower and slower
> and eventually runs out of memory. The problem seems to be the property
> ":childOrder" which gets larger and larger. The effect is the same as with
> Jackrabbit 2.x storing the list of child nodes in a node.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
