Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-7458

Cockpit with Postgres: Loading called historic process instances is slow

    XMLWordPrintable

    Details

      Description

      The Mybatis query cockpit.history.selectCalledHistoricProcessInstances (part of cockpit ee plugins) does not perform well on Postgres.

      Example scenario:

      • camunda 7.6.0-ee on Tomcat
      • Postgres 9.4
      • cardinality ACT_HI_PROCINST: 43.570
      • cardinality ACT_HI_ACTINST: 455.794
      • cardinality ACT_RE_PROCDEF: 121
      • cardinality ACT_RU_AUTHORIZATION: 3.214
      • Query has execution time of several minutes

      Attachments:

      • query.txt - the query
      • actual-query-plan.txt - the plan of the query in the above scenario
      • local-query-plan.txt - the plan of the query for a fresh Camunda distro
      • historic-instances-query.txt - the query that displays the list of historic process instances
      • historic-instances-query-plan.txt - the plan for this query in the above scenario

      Assessment:

      • According to actual-query-plan.txt, the costs of checking the authorizations for every process definition simply adds up
      • The plan for the regular historic instances query is much cheaper; perhaps we can change the called instances query to resemble the regular query so that it produces a similar plan

        Attachments

        1. actual-query-plan.txt
          6 kB
        2. historic-instances-query.txt
          5 kB
        3. historic-instances-query-plan.txt
          5 kB
        4. local-query-plan.txt
          4 kB
        5. query.txt
          5 kB

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            thorben.lindhauer Thorben Lindhauer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: