bigprincipalkk opened a new issue, #385: URL: https://github.com/apache/dubbo-go-hessian2/issues/385
主题：非常疑惑org.apache.dubbo.rpc.AdaptiveMetrics#getLoad，延迟惩罚和衰减的设计 <img width="997" height="588" alt="Image" src="https://github.com/user-attachments/assets/ab6e8a56-267d-4365-9f46-8838981c7494"; /> <img width="1045" height="662" alt="Image" src="https://github.com/user-attachments/assets/77f693c7-1916-4242-8305-bef74e284a23"; /> 问题： 1.只要服务端正常响应时，那么currentProviderTime和currentTime就被更新成serviceTime，那么紧接着有一次调用，触发getLoad，只要不发生时钟倒退一定会走到if (metrics.currentProviderTime == metrics.currentTime) 这个分支，那么也一定会满足，就会将lastLatency 置为 timeout * 2L，这个分支是极大概率的吧？那么实际的rt就会被覆盖掉，所以这里设计的是合理吗？ 2.metrics.lastLatency = metrics.lastLatency >> multiple衰减程度是否过快 希望大佬们可以帮忙解答下疑惑。抱拳 -- 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]
