[MGNLCDEP-77] Usage of NodeUtil.collectAllChildren may slow down resolution of dependencies Created: 19/Dec/14  Updated: 13/Mar/15  Resolved: 06/Mar/15

Status: Closed
Project: Content Dependencies
Component/s: None
Affects Version/s: 1.4.1
Fix Version/s: 1.4.2

Type: Bug Priority: Major
Reporter: Frank Sommer Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

The dependency tab shows dependencies from child pages, too. This is not the expected behaviour. Furthermore the loading time of the tab is bad.
Reason is that the DefaultDependencies class iterates over all child nodes and that is not quite fast.

LINE 172: Iterable<Node> children = NodeUtil.collectAllChildren(nodeReferencedFrom);


 Comments   
Comment by Federico Grilli [ 17/Feb/15 ]

I changed the title and description of the ticket as I think that the real issue here is using NodeUtil.collectAllChildren(..) which for large websites may become a performance killer. In this case, using a JCR SQL2 query should be much more efficient.

Generated at Mon Feb 12 00:12:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.