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
When AIMD works in conjunction with windowed limit, it might be way too careful in growing back after bursty spike (and, therefore, a backoff), because it has to proceed window size requests, before increasing limit by 1
My proposal is to add new method to AIMDLimit Builder, e.g.
public AIMDLimit.Builder growBy(int amount)
defaulting to 1 (current behavior)
The text was updated successfully, but these errors were encountered:
during lower load, limit won't grow, but previously this limit could've been pessimised and there has to be some mechanism to try to increase it
am I thinking in a right direction? How to deal with bursty load in that situation? I assume some sort of queueing should be applied then, but am I missing something crucial?
Maybe just smaller window size would solve that 🤔
IgorPerikov
added a commit
to IgorPerikov/concurrency-limits
that referenced
this issue
Dec 3, 2019
When AIMD works in conjunction with windowed limit, it might be way too careful in growing back after bursty spike (and, therefore, a backoff), because it has to proceed
window size
requests, before increasing limit by 1My proposal is to add new method to AIMDLimit Builder, e.g.
defaulting to 1 (current behavior)
The text was updated successfully, but these errors were encountered: