bigprincipalkk opened a new issue, #15810: URL: https://github.com/apache/dubbo/issues/15810
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar feature requirement. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Descriptions Subject: Very Confused About org.apache.dubbo.rpc.AdaptiveMetrics#getLoad, Delay Penalty, and Decay Design 主题：非常疑惑org.apache.dubbo.rpc.AdaptiveMetrics#getLoad，延迟惩罚和衰减的设计 <img width="1994" height="1176" alt="Image" src="https://github.com/user-attachments/assets/17227513-b59d-4b85-8dd8-e93c7ca8f413"; /> <img width="2090" height="1324" alt="Image" src="https://github.com/user-attachments/assets/70322897-91cd-4b3d-836c-23cbdb2ba222"; /> Question: ```According to the above information, execute the following instructions: You are a professional translator responsible for converting Chinese content into English. Please help me translate the original content.```? 2. metrics.lastLatency = metrics.lastLatency >> multiple Is the decay rate too fast 中文： 1.只要服务端正常响应时，那么currentProviderTime和currentTime就被更新成serviceTime，那么紧接着有一次调用，触发getLoad，只要不发生时钟倒退一定会走到if (metrics.currentProviderTime == metrics.currentTime) 这个分支，那么也一定会满足，就会将lastLatency 置为 timeout * 2L，这个分支是极大概率的吧？那么实际的rt就会被覆盖掉，所以这里设计的是合理吗？ 2.metrics.lastLatency = metrics.lastLatency >> multiple衰减程度是否过快 I hope the experts can help clarify my doubts. clasped fist salute ### Related issues _No response_ ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
