#Getting IP banned (?) when load testing using Locust (hosted in railway)

10 messages · Page 1 of 1 (latest)

torn thicket
#

I am trying to setup a 1-master, 5-slave Locust deployment.

It worked well until I hit 10k+ RPS. After that, all the requests sent by the Locust cluster seems to get a response of 403.

The testing setup is:

  • Go service in Project A
  • Locust cluster in Project B
  • They are bridged using cloudflared (a cloudflare tunnel running in projects A and B)
  • Locust cluster hits Go service using the domain exposed by the cloudflare tunnel

Is there something that can be done to accomplish this? Or am I stuck with managed load testing tools?

Personally, I would've preferred to use Artillery but its distributed option only supports AWS and Azure.

I decided to give Locust a shot since it dons a master-slave setup. I thought could be executed well in Railway, until the rate limiting hit.

sleek bay
#

We don't return a 403 under any circumstances.

#

If you were being rate limited, we would simply drop the packet.

torn thicket
#

Interesting. It might've been on Cloudflare's side then.

sleek bay
#

Yeah, undoubtedly.

torn thicket
#

In any case, a large scale Locust setup wouldn't work in Railway because of the rate limiting. I also noticed that setting a static IP address in a project seems to set the same address for all services under it so this will be rate limited, correct? Unless the services have a dynamic IP, which is unlikely. Or is there something for this niche already in the works for the platform?

sleek bay
#

We wouldn't rate limit our own IPs.

torn thicket
sleek bay
#

To test the raw RPS of your app, don't do any tunneling or anything with Cloudflare; do the testing directly over the private network.

torn thicket