Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-7238

A memory leak was discovered during a simple load test

XMLWordPrintable

    • False
    • None
    • False
    • ---
    • ---
    • 2022 Week 23-25 (from Jun 6)

      Runtime: quarkus

      Persistance: infinispan

      Prop: kogito.persistence.optimistic.lock=true

      Process (each sequntial task is executing async by jobs service):

      We use a simple load test for Jmeter to send POST requests, the frequency of which gradually increases (over 5 minutes) up to 10 tps.

      An example of a load script for Jmeter (for Jmeter to work correctly, you will need to install the plugin Concurrency Thread Group - https://jmeter-plugins.org/wiki/ConcurrencyThreadGroup/):

      kogito_service_step_async.jmx

      HeapDums and JFR-files:

      heapdump.zip

      heapdump_2.zip

      heapdump_3.zip

      kogito-bpmn-async.jfr

      kogito-bpmn-async_1.jfr
      Request example: curl -X POST -H 'Content-Type:application/json' -H 'Accept:application/json' -d '{"username" : "test"}' http://localhost:8080/sequential

      Screen memory leak:

        1. heapdump_2.zip
          37.34 MB
        2. heapdump_3.zip
          49.68 MB
        3. heapdump.zip
          11.01 MB
        4. kogito_service_step_async.jmx
          20 kB
        5. kogito-bpmn-async_1.jfr
          1.70 MB
        6. kogito-bpmn-async.jfr
          8.42 MB
        7. Screen_memory_leak.jpg
          Screen_memory_leak.jpg
          58 kB
        8. Sequential_scenario.png
          Sequential_scenario.png
          112 kB

            cnicolai@redhat.com Cristiano Nicolai
            shuriksamara Aleksandr Samarkin (Inactive)
            Marian Macik Marian Macik
            Marian Macik Marian Macik
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: