idbeta opened a new issue #3391: URL: https://github.com/apache/apisix/issues/3391
### why The current CI of apisix does not have performance testing. In order to avoid the problem of performance degradation of apisix caused by some modifications, it is necessary to increase the testing in this area. ### How **Determine testing scenarios** First, determine which scenarios need to be added for stress testing in CI. Because there are so many plug-ins in apisix, it is impossible to perform stress testing on every plugin. I read the performance test reports of several api gateway vendors and found that the most common scenarios is 1. only one simple route scenario 2. enabled limiting plugin scenario 3. enabled jwt plugin scenario 4. Enable a large number of different routes scenario **Determine benchmark data** In the environment of github action, use wrk to perform performance test on apisix in the specified scene. After 5 times tests, We find the lowest result and use it as the benchmark data. **Test** Perform performance test on apisix in CI to determine whether the QPS result is above the benchmark data. If the test result is lower than the benchmark data, it is considered that this modification has caused the performance of apisix to decrease. ### References https://konghq.com/api-microservices-management-benchmark-apigee https://www.nginx.com/resources/library/gigaom-api-report/ https://gist.github.com/membphis/137db97a4bf64d3653aa42f3e016bd01 ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org