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

Improve performance of deletion of asset manager properties.

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed and reviewed
    • Affects versions: 6.1
    • Fix versions: 6.3
    • Components: Backend Software

      Description

      We ran into problems with a valid bugfix (https://github.com/opencast/opencast/pull/580) because the SQL query (unknown to me) Opencast generates causes massive performance problems.

      On our test environment with more than 1 million entries in the table oc_assets_properties, I've tested some manuel naive SQL queries that would perform the job Opencast should.

      Mediapackage "795bf83d-9d3b-40a5-aae8-50df6f2b73ec" has 1071 properties (artificially generated).

      Here some benchmark results:

      select * from oc_assets_properties where mediapackage_id = "795bf83d-9d3b-40a5-aae8-50df6f2b73ec";
      approx. 3ms, results 1071 properties

      select * from oc_assets_properties where mediapackage_id = "795bf83d-9d3b-40a5-aae8-50df6f2b73ec" and namespace = "org.opencastproject.scheduler.ca.configuration";
      approx. 4ms, results 23 properties

      delete from oc_assets_properties where mediapackage_id = "795bf83d-9d3b-40a5-aae8-50df6f2b73ec" and namespace = "org.opencastproject.scheduler.ca.configuration";
      approx. 5ms

      This makes me think that the DSL Opencast uses (e.g. in PR #580 results in some very inefficient database queries). Not verified, though.

        TestRail: Results

          Attachments

            Issue links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  staubesv Sven Stauber
                • Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    TestRail: Cases