You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This does not work if newLat<10000 (10ms). Because the uint64_t cast is cutting the decimal places and avgLatencyUsec retains its value minus 1/10000 of it. But it would work if avgLatencyUsec type is a double.[[BR]][[BR]]
Another point is this condition:
uint64_t newLat=(uint64_t)(spent*1000000);
if(newLat < 1000000); // outliers of several minutes exist..
...
This means that timeouts does never count because the default network-timeout is 1500ms. That's bad. We suggest this:
In pdns_recursor.cc is this calculation for each user query:
This does not work if newLat<10000 (10ms). Because the uint64_t cast is cutting the decimal places and avgLatencyUsec retains its value minus 1/10000 of it. But it would work if avgLatencyUsec type is a double.[[BR]][[BR]]
Another point is this condition:
This means that timeouts does never count because the default network-timeout is 1500ms. That's bad. We suggest this:
And in this context we have a suggestion for a new Recursor setting:
With this option we can change the smoothing factor of the qa-latency value.
Attached you will find our suggestions as a patch. It's probably faulty coded. But it works for us.
The text was updated successfully, but these errors were encountered: