[MGNLPER-190] Find and document opportunities to improve the response time of periscope Created: 24/Apr/23  Updated: 19/Jun/23

Status: Open
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Spike Priority: Low
Reporter: Andrei Ichimescu Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by MGNLPER-191 Investigate the query time results fo... Closed
relation
is related to ADMINCTR-386 Findbar iterates over all nodes in th... Closed
is related to MGNLPER-165 Search queries are not executed concu... Closed
Template:
Date of First Response:
Epic Link: AuthorX improvements
Team: AuthorX

 Description   

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

Generated at Mon Feb 12 10:29:37 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.