[ https://issues.apache.org/jira/browse/OAK-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13587078#comment-13587078 ]
Thomas Mueller commented on OAK-656: ------------------------------------ OK, then it's just the current implementation that does it like that: {code} Node hello = session.getRootNode().addNode("hello"); System.out.println(hello.getPrimaryNodeType().getName()); nt:unstructured {code} I wonder if it would be a problem if we change the code to use a different node type. > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira