Performance

4 replies
961 views
Translate

Hi Aem-community,

Is it better use node iterator or querybuilder to find components on page and get properties of components?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

joerghohAccepted solution

Employee

When you need to find that on a single page, use the iterator approach; the static overhead of queries is typically higher than the cost of iterating.

joerghohAccepted solution

Employee

When you need to find that on a single page, use the iterator approach; the static overhead of queries is typically higher than the cost of iterating.

Translate

Anudeep_Garnepudi

New Participant

@keerthi0555

If you want to iterate through all the resources then go with iterator.

If you want a specific resource(s) with specific property then search using query builder.

Depends on your use case.

Translate

VeenaVikraman

New Participant

@keerthi0555 Node iteration is always faster and performance efficient that Query Builder. If you know the exact path to iterate and get the values , I would say use Node Iteration.

Please find a more detailed explanation from @joerghoh https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/child-node-iterating/m-p/305931/highlight/true#M28258

Translate

gkalyan

Level 1

@keerthi0555

It depends on couple of things: How complex is the query and how many nodes you are planning to traverse.

For a small number of nodes, iterating through JCR nodes using a node iterator is often more efficient.

For larger node sets or when dealing with more complex queries, it's generally better to set up Oak indexes and use QueryBuilder.

This best practices guides on queries and indexing might help, try checking this out

https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/deploying/practices/best-practices-for-queries-and-indexing

Translate

Sign up

Login with SSO

Login to the community

Login with SSO