Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3172

Optimize import bloats up the engine cache

XMLWordPrintable

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.1.0
    • None
    • backend
    • 145

      Context:

      • given:
        • I have an engine running with more than 1000 different definition key and version combinations
        • the heap space of the engine is limited (e.g. 4 GB of RAM)
        • I have an Optimize distribution that's configured to retrieve the data from the engine rest endpoint
      • when:
        • I start Optimize and with it the import
      • then:
        • the engine heap space increases a lot and even after garbage collection the used heap space does not decline
      • expected:
        • the engine does not get influenced by the Optimize import

      AT's:

      • optimize pages through decision/process definition data by their deployment time (needs CAM-11325)
      • one page fetched from the engine results in one import bulk to elasticsearch

      Hint:
      This is the reason for the increase in the heap space is the deployment cache since Optimize fetches all the definitions from the normal engine rest definition endpoint, which loads the deployments (XML included) into the in-memory cache.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              johannes.heinemann Johannes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: