[MGNLUI-5806] Possible performance issue while filtering tree view Created: 07/Apr/20  Updated: 21/May/21  Resolved: 07/Oct/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2.1
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Roman Kovařík Assignee: Unassigned
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLUI-5903 Column Filter: Improve the JCR data p... Closed
causality
caused by MGNLUI-5807 JCR Data provider filtering bugs/impr... Closed
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)
Epic Link: Column filtering

 Description   

MGNLUI-5671 fix filtering in tree view so the item if not filtered out if itself or any of its children matches.

This have a performance impact while processing item with huge amount of unmatched subnodes (~< 1000). User might wait for seconds/minutes for filtering to be finished. 

 

To reproduce, import attached export of contacts, allow nt:unstructured node type in the new contacts app and filter by nonexisting name.

 

AC:

  • TBD. How many items at what kind and level of degradation should we support?
  • Filtering should not take longer then 10sec (the default cache timeout to produce a warning)


 Comments   
Comment by Roman Kovařík [ 07/Oct/20 ]

Closing as superseeded by changing to flaf structure while filtering.

Generated at Mon Feb 12 09:30:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.