-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Rate limit by request time #18
Comments
Sounds good, can you elaborate a little bit more about what you have in mind? |
I was thinking of a new parameter to the
This will help us differentiate the requests weight on the system. I think it will add some power to the rate limit mechanism that can be enhanced further |
Thanks for the info @lchayoun. It's clear for me now, the only concern that I've you already pointed it's about the calculation being done in a later phase meaning new requests can jump in even thou the rate limit capacity has already being reached. |
I agree, but with a solid timeout I think it will be strong enough, do you want me to create a pull request on it? |
@lchayoun if you have time it would be awesome :) |
@lchayoun were you able to compile the project locally with your changes?
I believe it's related to
|
forked it again, seeing the same issue, taking a look |
@lchayoun thanks in a bunch |
@lchayoun do you have time to work on few tests for If you don't have time let me know. |
@lchayoun here we go v1.3.3.RELEASE. |
we have seen cases that rate limit by request number is not enough
sometimes a single request can be long and load the gateway
adding an option to measure the request time and add another limit option by time quetta might help in such cases
@marcosbarbero do you think it's a good idea?
The text was updated successfully, but these errors were encountered: