ranxuxin opened a new pull request, #9259:
URL: https://github.com/apache/apisix/pull/9259

   ### Description
   
   It improves the performance of apisix when there're more than 10 thousand 
routes and modifying one route. The new codes just modify the route data in 
routes array or the relative node of radixtree instead of creating the whole 
radixtree while one route was changed.
   
   After tesing as users at 1000 concurrency using ab tool while changing a 
route every one second, the overhead of cpu time is only 7%-8%. On the other 
hand, the apisix 2.9 costs near 100% cpu time.
   
   This patch is based the commit c924eb1cded079ec0d6279b211466b7d84a91ec2 in 
improveCreateRadixtree branch of apisix 2.9  .
   
   
   Fixes #9140
   
   ### Checklist
   
   - [ ] I have explained the need for this PR and the problem it solves
   - [ ] I have explained the changes or the new features added to this PR
   - [ ] I have added tests corresponding to this change
   - [ ] I have updated the documentation to reflect this change
   - [ ] I have verified that this change is backward compatible (If not, 
please discuss on the [APISIX mailing 
list](https://github.com/apache/apisix/tree/master#community) first)
   
   <!--
   
   Note
   
   1. Mark the PR as draft until it's ready to be reviewed.
   2. Always add/update tests for any changes unless you have a good reason.
   3. Always update the documentation to reflect the changes made in the PR.
   4. Make a new commit to resolve conversations instead of `push -f`.
   5. To resolve merge conflicts, merge master instead of rebasing.
   6. Use "request review" to notify the reviewer after making changes.
   7. Only a reviewer can mark a conversation as resolved.
   
   -->


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to