Get http://localhost:8080: read tcp [::1]:53942->[::1]:8080: read: connection reset by peer about boomer HOT 3 CLOSED

Seems ok with the --no-web flag. RPS on the server and Locust are about 80 RPS out.

from boomer.

1. Hatch rate is the growth rate of goroutines in boomer, or gevent coroutines in locust.
2. Request increase rate is the growth rate of request that boomer can generate per second.

If you want precise RPS control, --request-increase-rate is enough.

go run urlbash.go --request-increase-rate 10 --max-rps 1000

And set a 1000 users with a hatch rate of 1000.

$ go run server.go
2018/06/25 17:58:16 Rate: 1
2018/06/25 17:58:17 Rate: 10
2018/06/25 17:58:18 Rate: 21
2018/06/25 17:58:19 Rate: 29
2018/06/25 17:58:20 Rate: 41
2018/06/25 17:58:21 Rate: 49
2018/06/25 17:58:22 Rate: 61
2018/06/25 17:58:23 Rate: 69
2018/06/25 17:58:24 Rate: 80
2018/06/25 17:58:25 Rate: 90
2018/06/25 17:58:26 Rate: 100

BTW, stats data is reported to locust every 3 second, acting like a locust SlaveRunner in python. The RPS in Web UI is an average value. See this https://github.com/locustio/locust/blob/master/locust/stats.py#L307

from boomer.

Thanks for the clarification. I'll think I'll run with --no-web and amend the calculations on the go server.

from boomer.