24kpure opened a new pull request #8441: URL: https://github.com/apache/dubbo/pull/8441
## What is the purpose of the change As we know , most micro services are built based on cloud.However, there are several factors that affect the serviceļ¼for instance cpu steal ,network jitter and so on. LoadBalance should be more sensitive with running time of invoker when bad thing happens. ShortestResponseLoadBalance works not well for service has start for a long time so that average elapsed time changed little according to my past practice.Sliding window may be a good choice to solve this problem. ## Brief changelog Average elapsed time depends on statistics in sliding window. Once sliding window is end,a async thread will clear past data of all invokers, which I have thought for a long time. Segmented execution seems a good practice, but it would bring some potential risks.How about giving me some advice? ## Checklist - [x] Make sure there is a [GitHub_issue](https://github.com/apache/dubbo/issues) field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue. - [x] Each commit in the pull request should have a meaningful subject line and body. - [x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [x] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7 - [x] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in [dubbo samples](https://github.com/apache/dubbo-samples) project. - [x] GitHub Actions works fine on your own branch. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
