[MAGNOLIA-7691] Populating the last editor filter drop down of the find bar causes performance issues with many users Created: 28/Nov/19 Updated: 02/Dec/19 Resolved: 02/Dec/19 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Simon Lutz | Assignee: | Unassigned |
| Resolution: | Obsolete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| 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: | Periscope improvements | ||||||||||||
| Description |
|
To populate the last editor drop down list, the find bar queries the full user repository when a user clicks on the filter icon. This is leading to a massive performance degradation for clients with huge number of public users (up to an disfunct authoring instance). We need to find a more scalable way to provide the filtering capability for last editors. E.g.
|
| Comments |
| Comment by Michael Duerig [ 29/Nov/19 ] |
|
Turns out we could backport rkovarik's changes from findBarConfiguration:
suggestionCountPerSupplier: 3
defaultCountPerSupplier: 10
editorRoles:
- superuser
The default is no exclusions, but customer affected by issues with to many users in that list could just restrict it by configuration to their editors.
slutz, WDYT? |
| Comment by Michael Duerig [ 02/Dec/19 ] |
|
This has in the meanwhile been superseded by |