Hello Dev team, I am working on an AEM project where we have a large number of child nodes that need to be created. I have a few questions around performance.
We are using AEM 6.1 which utilizes Oak 1.2.7. A few questions: 1. I know that there is no “actual” limit to child nodes, but In your experience, is there a limit to child nodes over which we will see performance impact? or instability of some sort? and what would be your recommended “virtual” number of child nodes? 2. Will read/writing one node which has, lets say 10,000 sibling be problematic for any reason? 3. I know that there are node types that have ordered vs unordered children. When does Oak actually order the child nodes? on read? Thank you for your time, Ahmed
