zrlw commented on PR #10745: URL: https://github.com/apache/dubbo/pull/10745#issuecomment-3815785863
@ningboliu ``` 1. As long as the server responds normally, the currentProviderTime and currentTime will be updated to serviceTime. Then there will be a call to trigger getLoad. As long as there is no clock back, the branch if (metrics. currentProviderTime==metrics. currentTime) will be reached. Then it will be satisfied. The lastLatency will be set to timeout * 2L. Is this branch a maximum probability? So the actual RT will be overwritten, so is the design here reasonable? 2. As long as getLoad is called once, metrics. CurrentProvider Time==metrics. CurrentTime will not be satisfied, so what is the design purpose of this branch? 3. metrics. lastLatency = metrics. lastLatency >> multiple; Does the decay rate occur too quickly? ``` see details at https://github.com/apache/dubbo/issues/15810 -- 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]
