Maximum number of nodes on CRX AEM can have without performance taking hit

[Balaram_Rudra]

I am saving the application data on CRX under the /content now. I now suspect the size of the data/nodes is too big. What is the maximum size of data (and number of nodes) one can have under /content node for an optimal performance? What are the factors/checks on AEM that indicate the node size is bigger than what it should be?  How to optimize the performance when there are huge number of nodes under /content node? 

[Ganthimathi_R]

@Balaram_Rudra please refer the following posts:

https://jackrabbit.apache.org/oak/docs/dos_and_donts.html

https://cqdump.joerghoh.de/2015/07/09/1000-nodes-per-folder-and-oak-orderable-nodes/

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/5000-pages-under-single-no...

 Hope this helps.

[Balaram_Rudra]

Thank you @Ganthimathi_R, this definitely helped. I am also looking for information as to what the amount of data or number of nodes AEM can handle (not necessary under one node) without giving in on the performance. Is there any recommendation from adobe on this (for a given hardware specification) ?

[Jörg_Hoh · Accepted solution]

If you save thousands of nodes below /content, try to open the siteadmin and check the performance.

The general rule of thumb of not to have more than 1000 child nodes is because of the browsers and the UI, and less because of the repository itself.

[Mayank_Gandhi]

@Balaram_Rudra 

The way a content repository is structured can impact performance as well. For best performance, the number of child nodes attached to individual nodes in a content repository should not exceed 1,000 (as a general rule)

If you are concerned about the binaries and non-binaries then this has the best explanation about handling the node size

https://cqdump.joerghoh.de/2022/07/05/whats-the-maximum-size-of-a-node-in-jcr-aem/