[MGNLUI-8683] Findbar filter is slow with many users Created: 06/Feb/24  Updated: 06/Feb/24

Status: Open
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.3.0
Fix Version/s: None

Type: Improvement Priority: Low
Reporter: Michael Duerig Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: searchx
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File filter.png     PNG File new filter.png    
Issue Links:
Problem/Incident
is caused by MGNLUI-5523 Findbar queries all public users on i... 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)
Date of First Response:
Epic Link: Throughput improvements

 Description   

Issue

Clicking on the filter icon in the findbar causes all users to be loaded. With many users this can be slow.

Context

This is a follow up to MGNLUI-5523 where loading the users was deferred to the point where he filter icon is clicked.

In 6.3 loading might get deferred even further to the point where an actual editor filter is added.

Discovery

  • How big is the current impact? With how many users can the current implementation reasonably deal (using standard PaaS instance size as a reference)?
  • Can we lazy load the users (similar to grids)?
  • Can we paginate the users so we don't have to load all of them?
  • Should we cap the number of users we support in the filter? How would that be communicated to the user and what alternatives do we offer?
  • Do we leave it as is for now?


 Comments   
Comment by Michael Duerig [ 06/Feb/24 ]

/cc ldelnevo (for visibility)

Comment by Roman Kovařík [ 06/Feb/24 ]

It would be nice to have a use case before investing time in this. In all likelihood, there is no common scenario where you would genuinely need to display thousands of users in the dropdown. As Magnolia cannot determine which users are editors, the editorRoles configuration in the find bar already addresses this by allowing specification.

Comment by Michael Duerig [ 06/Feb/24 ]

Ack rkovarik , the ticket priority is low and I added "Do we leave it as is for now?" as a question for discovery.

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