Best Practices and Examples

Performance tests for a service should not only verify the expected throughput, capacity, etc., but should also push the service to its defined limits to document its behavior (alerts generated, resource consumption, stability, etc.) as it approaches, reaches, and exceeds those service limits. 

For example documentation see: 

• RHOSAK Performance and Scale Test Plan (for the expanded service limits)
• Streams Test Limits Request  (tracked: MSPSR-11)

For example code see:

The RHOSAK automated performance tests are implemented in the Open Messaging Benchmark (OMB) framework. These tests are triggered on demand, no regular frequency. 

• Repo: https://gitlab.cee.redhat.com/mk-bin-packing/mk-performance-tests 
• Pipelines: https://main-jenkins-csb-mas.apps.ocp-c1.prod.psi.redhat.com/job/performance/job/kas-performance-tests 

Steps to Follow to Contribute a New Automated Test:
https://gitlab.cee.redhat.com/mk-bin-packing/mk-performance-tests/-/blob/master/README.md 

Where to Get Help

QE works closely with the Performance & Scale Team (Pradeep Surisetty, Lead) in the design and development of performance related tests.  QE leverages their past experience and expertise in the design of tests and in the best use of performance test tools.

For details see this source page.