[MGNLUI-8559] Investigate observation delays Created: 01/Dec/23  Updated: 01/Feb/24

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

Type: Story Priority: Neutral
Reporter: Adam Siska Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: dx-core-6.3
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLUI-8560 Implementation Sub-task To Do  
MGNLUI-8561 Review Sub-task To Do  
MGNLUI-8562 Pre-Integration QA Sub-task To Do  
MGNLUI-8563 QA Sub-task To Do  
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)
Documentation update required:
Yes
Epic Link: ui push scalability
Work Started:
Approved:
Yes

 Description   

JcrObservation mechanism has configurable delays since MGNLUI-8438. The default values for observation delays weren't tackled during this effort. See JcrObservationDefinition delay and maxDelay values.

We can invest more time to investigate if there are better values for default delays and change them to achieve better performance without lack of UX.

Also as part of this ticket we can investigate what values are reasonable to use when performance issues happen or more generally provide some procedure to derive these numbers for particular instances/number of items in workspace/number of sites/etc.. and document them for customers suffering from different performance issues.

Dev context: https://git.magnolia-cms.com/projects/PLATFORM/repos/ui/pull-requests/2532/overview?commentId=124060


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