Upcoming stress test
yanneves
PROOP

a year ago

Hi team,

Wanted to give you a heads up that I'm planning a community event that will stress test on our infrastructure.

Current plan is to run the event over three rounds:

  1. Saturday, 11th Jan @ 20:00 GMT

  2. Monday, 13th Jan @ 09:00 GMT

  3. Wednesday, 15th Jan @ 23:00 GMT

This will rely on your new multi-region support.

I'll initially scale the cluster to:

  • 12 Browser Stack servers across 3 (US,EU,ASIA) regions.

  • 6 WebSockets servers (same regions)

  • 3 SvelteKit UI servers (same regions)

Assuming this falls over, I'll allocate more Browser Stack instances as this is the most probable bottleneck.

What's the best way to monitor the server resources in Railway?

Thanks,

Yann

Solved

4 Replies

Hi Yann,

Thank you for the heads up.

Given that you're managing multiple services, creating an observability dashboard in your Railway project (https://docs.railway.com/guides/observability) is the way to go.

We generally advise against doing artificial load tests against our platform, but I understand you'll want some level of confidence that Railway can meet your scaling needs, so just keep in mind that you might get rate-limited by some of our DoS protection mechanisms.


Status changed to Awaiting User Response Railway about 1 year ago


yanneves
PROOP

a year ago

Thanks for the link, that's what I'm after, will read up.

Good to know. This isn't an artificial load test, it's a genuine community event / marketing campaign. But from a technical point of view it will test our deployments under stress.


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

Ah good to know, then you are unlikely to run into any ddos limitations at scale given the traffic will be relatively organic.

Some single user (IP) doing a boatload of concurrent requests would still get limited, but that would only affect them since they sent disingenuous traffic.

Let us know if you have anymore questions!


Status changed to Awaiting User Response Railway about 1 year ago


yanneves
PROOP

a year ago

Pleased to report Railway didn't break a sweat. Great job team!


Status changed to Awaiting Railway Response Railway about 1 year ago


Status changed to Solved chandrika about 1 year ago


Loading...