New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does not work when parameters are large #50
Comments
I observed similar behaviour, e.g.
No key for entry Maybe I don't understand the GCRA algorithm, but from my POV this clearly is a very serious bug. Can please author comment? Is this project still alive? |
Hello @brandur, could you please clarify semantics of max_burst parameter? |
I'm having the same issue. Working with max_burst and count_per_period with numbers like 100 or 300 or 500. For instance: I ejecute the same command and the numbers does not change. Please, @brandur can you help? |
Depending on used parameters (count, max_burst and period) the algorithm sets the expiration of keys only for fraction of second in some cases. |
I downloaded the latest version and used it with redis server version 5.0.7, I tested cl.throttle command with both small and large parameters (small capacity + refilling speed, large capacity + refilling speed). The result shows that when capacity and refilling speed are both large, like 6000 at most, and every second 6000 (kind like a tps throttling), it does not work at all. Besides, cl.throttle a 6000 6000 1, gives the third parameter larger than 6000 capacity, very odd.
The text was updated successfully, but these errors were encountered: