-
Spike
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
Find and document opportunities to improve the response time of periscope
Use findings from MGNLPER-165 if applicable.
Open followup tickets after discovery is being done.
We want to spend 5 days max investigating this please
Things to consider:
- Caching results per user (we need to be aware of some customers with huge user-base)
- Pagination -> limit the supplier results in query vs in findbar.
- Smart Search Suppliers, e.g: findbar shows 100 results, if the first search supplier returns 95 results, the second one should have a limit of 5 being applied.
- Do we iterate over all nodes?
- UI framework limitation (multiple queries being executed due to vaadin and UI framework architecture)
- consider restructuring of the periscope if it will make life more easier to implement the followup tickets
- is cloned by
-
MGNLPER-191 Investigate the query time results for Pages in Big Data scenario
- Closed
- is related to
-
ADMINCTR-386 Findbar iterates over all nodes in the pages/assets app on presenting the ui
- Closed
-
MGNLPER-165 Search queries are not executed concurrently
- Closed