adjust flow to iterate speed
higher ft1sha1 iterate interval (not fixing it yet)
This commit is contained in:
parent
b35babe3f8
commit
6d7d643207
@ -7,7 +7,9 @@
|
|||||||
|
|
||||||
float FlowOnly::getCurrentDelay(void) const {
|
float FlowOnly::getCurrentDelay(void) const {
|
||||||
// below 1ms is useless
|
// below 1ms is useless
|
||||||
return std::clamp(_rtt_ema, 0.001f, RTT_MAX);
|
//return std::clamp(_rtt_ema, 0.001f, RTT_MAX);
|
||||||
|
// the current iterate rate min is 5ms
|
||||||
|
return std::clamp(_rtt_ema, 0.005f, RTT_MAX);
|
||||||
}
|
}
|
||||||
|
|
||||||
void FlowOnly::addRTT(float new_delay) {
|
void FlowOnly::addRTT(float new_delay) {
|
||||||
|
@ -467,9 +467,9 @@ float SHA1_NGCFT1::iterate(float delta) {
|
|||||||
if (_peer_open_requests.empty()) {
|
if (_peer_open_requests.empty()) {
|
||||||
return 2.f;
|
return 2.f;
|
||||||
} else {
|
} else {
|
||||||
// pretty conservative and should be ajusted on a per peer, per delay basis
|
// ft1 will go lower for us, if we have unresolved info,
|
||||||
// seems to do the trick
|
// we dont want to be stuck in a high tickrate
|
||||||
return 0.05f;
|
return 0.5f;
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user