Uploaded image for project: 'Opencast'
  1. MH-11700

workflow/statistics.json as called by old AdminUI is very inefficient

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Won't Fix
    • Affects versions: 1.6.3
    • Fix versions: 1.7.0
    • Components: RESTful Interfaces
    • Labels:
      None
    • Severity:
      Performance
    • Steps to reproduce:
      Hide
      The old admin UI polls workflow/statistics.json to update the number of workflows in each category on the Recordings tab. The Admin UI is only concerned with the total WFs in each state and the state of operations in the Scheduling WF.

      However the endpoint returns data for every operation in non-completed state for every workflow. This is a lot of unused data.

      Further the calls to the workflowindex are very inefficient getting state counts for "every operation x workflow" => 100 queries

      With a separate solr server the tomcat logs can grow very rapidly with a single admin window polling every 5s.

      Finally the calls to workflow index do use the default row count of 10 so documents are returned for every query.
      Show
      The old admin UI polls workflow/statistics.json to update the number of workflows in each category on the Recordings tab. The Admin UI is only concerned with the total WFs in each state and the state of operations in the Scheduling WF. However the endpoint returns data for every operation in non-completed state for every workflow. This is a lot of unused data. Further the calls to the workflowindex are very inefficient getting state counts for "every operation x workflow" => 100 queries With a separate solr server the tomcat logs can grow very rapidly with a single admin window polling every 5s. Finally the calls to workflow index do use the default row count of 10 so documents are returned for every query.
    • Tags (folksonomy):

      TestRail: Results

        Attachments

          Activity

            People

            • Assignee:
              jamesp James Perrin (Inactive)
              Reporter:
              james.perrin James Perrin
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                TestRail: Cases