Uploaded image for project: 'Periscope'
  1. Periscope
  2. MGNLPER-190

Find and document opportunities to improve the response time of periscope

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Low 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

            Unassigned Unassigned
            aichimescu Andrei Ichimescu
            AuthorX
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: