What is the impact on aem 6.3 instance if the proprties in a node increases

[manisha594391]

Is there any restriction to number of properties those could be added to a node in aem 6.3?

Also , is there any impact on the instance if the number of properties in a content node increases?

How is the instance impacted with more number of properties.

This is specific with respect to aem 6.3 version.

[berliant · Accepted solution]

There is no known limitation on the number of node's properties. For most of the use cases, you need to proactively index those properties that are used for a search.

[Bharath_valse]

Below link has few additional context with maintenance in mind

https://forums.adobe.com/message/10473803#10473803

[hamidk92094312]

On top of what Leo mentioned you should actively check the logs to see if there has been any traversal query and if there is such query just create a relevant index. You can use Oak index definition generator for this purpose.

Oak Utilities : Index Definition Generator 

[manisha594391]

@hamidk92094312@berliant We do not have any search requirement associated with this node and properties.

Its just like we want to persist it on jcr and fetch the properties using sling/jcr to render the page.

Will it still have any issue ?

[hamidk92094312]

You may not have a "search" requirements yourself. When we mentioned "search" it does not imply a search feature or something like that. Oftentimes AEM needs to fetch properties/nodes to assemble and render pages and for doing this a query is built and executed behind the scene . We are referring to that search query. When there is a large number of nodes to traverse then performance issues may arise in which case creating an index would help to improve the performance.

[berliant]

I don't think that having a large number of nodes' properties will be an issue.