[
https://issues.apache.org/jira/browse/OAK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14044618#comment-14044618
]
Lukas Kahwe Smith commented on OAK-656:
---------------------------------------
order-ability is one of the big features imho from JCR, so I think optimizing
performance here is important. lets say I have a news paper with articles
partitioned by day. these can still easily get in the hundreds but I still want
to be able to manually affect the sorting. if Oak cannot efficiently deal with
20+ children it seems like its giving up on a large number of use cases
> 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)
