-
Notifications
You must be signed in to change notification settings - Fork 245
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
Get http://localhost:8080: readLoopPeekFailLocked: read tcp [::1]:60834->[::1]:8080: read: connection reset by peer #32
Comments
Ran:
Now:
|
Don't put a time.Sleep in your code, you may need boomer's max RPS support. Try to run with --max-rps 10000. |
Thanks, I noticed that last night. Any chance of a timed linear ramp-up to 10,000 RPS? |
Do you feel there is any value to the Locust UI now, especially users and hatch rate? |
You mean locustio/locust#646 ? Locust has no support for RPS control, so far. |
Sorry for the spam everyone, but I think this is what you are inferring. However, the hatch rate, Locust RPS and server RPS are out of sync.
|
The hatch rate is related to the number of goroutines(users), not the RPS. In this case, 10 users or 1000 users, make no difference. If you run with --max-rps 1000, the RPS of both locust and server, should be very close. |
And they are, thank you very much. Do you think we could also increase file descriptors, decrease TCP TIME_WAIT and increase idleConnections? |
Only if you want to know how many long connections the server can handle, not the max requests it can process per second. |
I am willing to pay a bounty to add a linear ramp-up as a command line flag (e.g.) -rps=1 which would increase to the --max-rps. adrian underscore lewis at hushmail dot com. |
Adding a command line flag (e.g.) request-increase-rate=1 which would increase from zero to -max-rps, or infinity if max-rps is disabled. |
Hi @myzhan Shall I put the request on here: https://www.bountysource.com? |
Cool, thanks for letting me know such a website. |
Running the example test here and 10000 users with a hatch rate of 50. I get:
I have had it running at 30,000 users with one Boomer.
mac OS Sierra, 8GB, 2 cores
Thanks
The text was updated successfully, but these errors were encountered: