dspo opened a new pull request, #2475:
URL: https://github.com/apache/apisix-ingress-controller/pull/2475
<!-- Please answer these questions before submitting a pull request -->
### Type of change:
<!-- Please delete options that are not relevant. -->
<!-- Select all the options from below that matches the type your PR best -->
- [ ] Bugfix
- [ ] New feature provided
- [ ] Improve performance
- [ ] Backport patches
- [ ] Documentation
- [ ] Refactor
- [x] Chore
- [x] CI/CD or Tests
### What this PR does / why we need it:
This PR adds stress tests for apisix-ingress-controller.
#### Test Cases
- Apply 2000 prepared ApisixRoutes to the cluster. When all ApisixRoutes are
created, start timing. Use the data plane Control API to count the number of
services on the data plane until it reaches 2000, then stop timing. This is
used to calculate the time it takes for apisix-ingress-controller to
synchronize 2000 CRDs.
- Count the time it takes to update one of the 2000 existing ApisixRoutes
and make it effective. The calculation method is: based on the 2000 existing
ApisixRoutes, update one of them and poll the corresponding route until the
route takes effect.
#### How to run the tests ?
```shell
TEST_DIR=./test/e2e/load-test/ PROVIDER_TYPE=apisix-standalone
PROVIDER_SYNC_PERIOD=5s make e2e-test
```
result example:
```text
======================TEST RESULT ProviderSyncPeriod
5s===============================
Test Case Time
Required
--------------------------------------------------------------------------------------
Apply 2000 ApisixRoutes
8.660792908s
Update a single ApisixRoute base on 2000 ApisixRoutes
9.753447004s
======================================================================================
```
<!--- Why is this change required? What problem does it solve? -->
<!--- If it fixes an open issue, please link to the issue here. -->
### Pre-submission checklist:
<!--
Please follow the requirements:
1. Use Draft if the PR is not ready to be reviewed
2. Test is required for the feat/fix PR, unless you have a good reason
3. Doc is required for the feat PR
4. Use a new commit to resolve review instead of `push -f`
5. Use "request review" to notify the reviewer once you have resolved the
review
-->
- [x] Did you explain what problem does this PR solve? Or what new features
have been added?
- [x] Have you added corresponding test cases?
- [ ] Have you modified the corresponding document?
- [x] Is this PR backward compatible? **If it is not backward compatible,
please discuss on the [mailing
list](https://github.com/apache/apisix-ingress-controller#community) first**
--
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.
To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
