Railway Metal slowing db connection
arizagadd
PROOP

8 months ago

Hi Support, since upgrading my MySQL instance to Railway Metal I’ve noticed a dramatic increase in round-trip times—previously my queries consistently returned in under 500 ms, but now most requests take 1.3–2 seconds, even though no errors appear in my logs. The browser’s “turtle” icon frequently flags the delays, and my users experience sluggish page loads and unresponsive interactive features. I’ve measured network latency from my app pods to the database and seen it remain permanently elevated, and in a prior incident I temporarily restored performance by creating a fresh instance and deleting the old one. Could you help me determine if Railway Metal introduces additional network hops or proxy layers, suggest any connection-pool or TLS configuration changes, or check cluster health on your end to resolve these higher latencies?

Solved

8 Replies

itsrems
EMPLOYEE

8 months ago

Your svelte and rutaflow-app services are still running on legacy regions. You'll want to swap them to same metal region as your other services (US West - California) to prevent added latency if communicating between services.

Are you using private networking to communicate with your database ?


Status changed to Awaiting User Response Railway 8 months ago


arizagadd
PROOP

8 months ago

I’ve already moved my services to the US West – California region and enabled private networking for database communication, but I’m still seeing the same high latency that’s impacting my apps. Could you help me understand why the private network isn’t improving performance and what else I might need to configure?


Status changed to Awaiting Railway Response Railway 8 months ago


itsrems
EMPLOYEE

8 months ago

Are the requests still taking >1s through the private network ?


Status changed to Awaiting User Response Railway 8 months ago


arizagadd
PROOP

7 months ago

Yes, the requests are still taking over 1 second—almost 2 seconds—even with private networking. I actually noticed they take even longer now frowning_face emoji.


Status changed to Awaiting Railway Response Railway 8 months ago


Railway
BOT

7 months ago

Hello!

We've escalated your issue to our engineering team.

We aim to provide an update within 1 business day.

Please reply to this thread if you have any questions!

Status changed to Awaiting User Response Railway 8 months ago


Railway
BOT

7 months ago

❌ The internal ticket MySQL performance issues on metal has been marked as canceled.


itsrems
EMPLOYEE

7 months ago

Your services are not using private networking to communicate with your database. Please see documentation here: https://docs.railway.com/reference/private-networking


arizagadd
PROOP

7 months ago

I decided to make tests with the private networking in my development environment in the service that has my api and i noticed that the requests last longer, the latency increased so i didn't change anything in production, thath's why i'm not using in all my enviroments the private networking.
I add two screenshots that has the timing of the development enviroment using the private networking and the second is from my production enviroment using the public networking.


Status changed to Awaiting Railway Response Railway 7 months ago


brody
EMPLOYEE

7 months ago

Comparing response times in production against the development environment would not be a good apples to apples comparison.

Please switch to the private network and then we can go from there, using the public network is not something we can recommend.


Status changed to Awaiting User Response Railway 7 months ago


Railway
BOT

6 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 6 months ago


Loading...