Way too many events allowed when burst is not 1 about redis_rate HOT 4 CLOSED

If you mean a link to my code, not yet, no.

from redis_rate.

Perhaps I'm just not understanding how this new algorithm operates. I guess the burst is the initial token count and you can have any number of them, such that the use rate won't match the actual rate limit set. Unfortunately not the way I was hoping this package would work...

from redis_rate.

I guess I'll close this; I was hoping it'd behave like a rolling window rate limiter, but that isn't the case. Just wrote my own with sorted sets of timestamps instead. 😛

from redis_rate.

Do you have a link to share? :)

I guess the burst is the initial token count and you can have any number of them, such that the use rate won't match the actual rate limit set.

Yeah, you may think of it as the bucket size with is re-filled at the given rate.

from redis_rate.