[MGNLUI-6443] Use push instead of polling to update search results Created: 07/Dec/20  Updated: 07/Oct/21  Resolved: 05/Jan/21

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

Type: Task Priority: Major
Reporter: Sönke Schmidt Assignee: Šimon Demočko
Resolution: Fixed Votes: 0
Labels: performance
Remaining Estimate: Not Specified
Time Spent: 3h 29m
Original Estimate: Not Specified

Issue Links:
Problem/Incident
causes MGNLUI-6899 Jetty libraries on the classpath make... Closed
dependency
is depended upon by MGNLPER-135 Long running searches cause performan... Closed
relation
is related to MGNLUI-6494 FindBarTest.configuredOrderIsRespecte... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Epic Link: UI framework implementation
Sprint: UI FW 18 (christmas), UI FW 19
Story Points: 8

 Description   

Running searches against a very big workspace using info.magnolia.periscope.search.jcr.JcrSearchResultSupplier might take a considerable amount of time. Especially during the initial search after logging in to Admin Central. E.g. as soon as you log in, a search is run against the website workspace without a query term.

As long as the search is running Vaadin UIDL requests are constantly sent to Magnolia.
Depending on network latency, these requests may take some time to complete. E.g. 100 - 200 ms.
This may results in Admin Central UI becoming very sluggish and sometimes impossible to navigate as long as the search is running.

Problem statement

The polling could be endless with very long searches over large repositories.

Solution

Replace polls with a push.

Together with MGNLUI-6398 this should solve MGNLPER-135

 


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