Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-11025

Perf test 2.15 - "extra large" 100M SKU - multi profile

XMLWordPrintable

    • RHOAM Sprint 57, RHOAM Sprint 58

      WHAT
      Replicate as much as possible the performance testing done in 2.8 in order to compare to 2.15

      HOW

      1. Run a 6 hour sustained rate test at 1157 rps with a `standard` profile - use standard APIManager
      2. Run a 6 hour sustained rate test at 1157 rps with a `simple` profile - use simple APIManager
      3. Run a 1 hour peak rate test at 1736 rps with a `standard` profile - use standard APIManager
      4. Run a 1 hour peak rate test at 1736 rps with a `simple` profile - use simple APIManager
      5. Run a 1 hour peak rate test at 4628 rps with a `simple` profile - use simple APIManager

      rps is users_per_second

      Record parameters used in Hyperfoil. Add HTML to JIRA
      We can also consider switching to Locust if reasons are strong enough

      VERIFY / OBSERVE
      For each test ensure that:

      • Resources allocated are inline with SKU/Core/Daily API Requests recommendations and previous test runs.
      • Observe total CPU and memory usage across the 3 scaling pods, backend worker, backend listener, apicast prod
      • Compare totals to 2.8 totals
      • Ensure that 3scale remains healthy during the tests
      • No alerts firing, no pods crashing, 3scale not reporting errors (product analytics more accurate than testing tool)

      References
      See test results here Along with extrapolated spreadsheet with resources usage

        1. report_1715698893.2428293.html
          1.29 MB
        2. total_requests_per_second_1715698588.png
          total_requests_per_second_1715698588.png
          47 kB
        3. report_1715761068.9096596.html
          827 kB
        4. total_requests_per_second_1715762930.png
          total_requests_per_second_1715762930.png
          54 kB
        5. k6 report-15-05-2024.html
          302 kB
        6. Screenshot from 2024-05-15 12-48-58.png
          Screenshot from 2024-05-15 12-48-58.png
          135 kB
        7. screenshot-1.png
          screenshot-1.png
          183 kB
        8. report_1715900430.862058.html
          1.29 MB
        9. total_requests_per_second_1715900409.png
          total_requests_per_second_1715900409.png
          57 kB
        10. screenshot-2.png
          screenshot-2.png
          20 kB
        11. image-2024-05-17-09-25-11-764.png
          image-2024-05-17-09-25-11-764.png
          114 kB
        12. image-2024-05-17-09-25-43-983.png
          image-2024-05-17-09-25-43-983.png
          35 kB
        13. image-2024-05-17-09-26-15-423.png
          image-2024-05-17-09-26-15-423.png
          121 kB
        14. image-2024-05-17-09-26-50-042.png
          image-2024-05-17-09-26-50-042.png
          139 kB
        15. image-2024-05-17-09-27-16-739.png
          image-2024-05-17-09-27-16-739.png
          44 kB
        16. image-2024-05-17-09-27-51-521.png
          image-2024-05-17-09-27-51-521.png
          81 kB
        17. k6 report 17-05-2024.html
          235 kB

              Unassigned Unassigned
              bgallagh@redhat.com Brian Gallagher
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: