WHY
A full round of performance testing was not done for several releases of 3scale. Given the introduction of async and HPA, 2.15 is a good time to re-run these tests and bring the process up to date, including reevaluating the tooling and process.
We also want to ensure we are still inline with BU SKUs for 3scale

*HOW *

• Evaluate how performance testing was done in the past.
• Redefine the process and tooling required
• Run tests
• Document for future execution

Ensure that SKUs are still adhered to

REFERENCE MATERIAL

This benchmarks drive should have all the material about 3scale performance testing.

Check only latest tests, highlighting:

• AMP 2.8 Performance Testing
• 3scale AMP Performance and Recommended Configs AMP 2.8
• 3scale AMP Performance (2.8 + apisonator async + HPA)

2.9 Performance testing was started https://issues.redhat.com/browse/THREESCALE-5901, but never finished it and jira was closed due to inactivity. From Eguzki: "There was an issue with openshift ingress gateway, so we were thinking on generating stress traffic from within the cluster, but it never happened."