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
The default Guava RateLimiter initializer creates a rate limiter with 0 permits, and starts acquiring them. This causes an unexpected behaviour, where at the beginning of the rate limiters lifetime the rate limit is much lower that specified.
// rate limits way more aggressively than `permitsPerSecond` at startRateLimiter.create(permitsPerSecond)
What did you want to happen?
Setting the warm up time to zero means that max permits are available at start.
What happened?
The default Guava RateLimiter initializer creates a rate limiter with 0 permits, and starts acquiring them. This causes an unexpected behaviour, where at the beginning of the rate limiters lifetime the rate limit is much lower that specified.
What did you want to happen?
Setting the warm up time to zero means that max permits are available at start.
The text was updated successfully, but these errors were encountered: