-
Notifications
You must be signed in to change notification settings - Fork 887
scaletest: How can I avoid API rate limits? #5531
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
Comments
I think that is the desired behavior, based on the help text:
I wish the scale test was able to bypass it somehow |
Yea, I would argue all rate limits are to prevent DOS attacks though. |
There's a |
@ammario the load tests use that header but only when making requests as site owner, this is the login endpoint to login to a new user so it has a ratelimit of it's own. I think we just need to make that ratelimit configurable also :/ |
I'm attempting to run a scale test on my Kubernetes cluster with the following command:
However, I'm only able to create roughly ~60 concurrent workspaces as I run into a rate limit error:
== FAIL: workspacebuild/794 Error: login as new user: POST http://coder.example.com/api/v2/users/login: unexpected status code 429: You've been rate limited for sending more than 60 requests in 1m0s.
I have also set
CODER_API_RATE_LIMIT=-1
for mycoder server
, but saw that some routes are still rate limited, regardless of this value:The text was updated successfully, but these errors were encountered: