9 months ago
Our app is running super slow - would normally think it's on our end, but after attempting to migrate to metal I think it's on the Railway routing side. We're still on legacy after running into issues. Performance issues are intolerable.
5 Replies
9 months ago
Hello,
I'm sorry to hear that your experience on Metal isn't what you expected. I'm here to help you sort out any issues that could be preventing you from having a great experience on Metal.
So the two main issues I see that cause what is observable as degraded performance are -
1. Not having all the services in the same region.
2. Not using the Private Network for all communications.
And from a quick look at your project, I can see that #2 is likely the reason you are observing regressed perfoamce, you are doing communications to Redis and Postgis over the public network.
By doing communications over the Public TCP Proxy while your services are on Metal, there are a few extra network hops because the TCP Proxy itself is still hosted on Legacy.
The solution is simply to use the private network for all communication where applicable; this ensures the network requests will take the absolute shortest path from and to your services, such as PostGIS or Redis.
So that path forward here would be to ensure you are using the private network, and then you can move your services back to Metal. At that point, your application should be performing perfectly again!
If you have any questions, please do let me know!
Best,
Brody
Status changed to Awaiting User Response Railway • 10 months ago
brody
Hello,I'm sorry to hear that your experience on Metal isn't what you expected. I'm here to help you sort out any issues that could be preventing you from having a great experience on Metal.So the two main issues I see that cause what is observable as degraded performance are -1. Not having all the services in the same region.2. Not using the Private Network for all communications.And from a quick look at your project, I can see that #2 is likely the reason you are observing regressed perfoamce, you are doing communications to Redis and Postgis over the public network.By doing communications over the Public TCP Proxy while your services are on Metal, there are a few extra network hops because the TCP Proxy itself is still hosted on Legacy.The solution is simply to use the private network for all communication where applicable; this ensures the network requests will take the absolute shortest path from and to your services, such as PostGIS or Redis.So that path forward here would be to ensure you are using the private network, and then you can move your services back to Metal. At that point, your application should be performing perfectly again!If you have any questions, please do let me know!Best,Brody
9 months ago
We've tried the private network and get DNS resolution issues. Would love someone walking me through exactly what the values should be because I set them to what seems to be the proper values and get the name resolution issues.
Let me know what next steps would look like.
Status changed to Awaiting Railway Response Railway • 10 months ago
9 months ago
Hey Justin, could you share what you're setting the values to and the exact error you were seeing?
Redis should be along: redis://${{REDIS_USER}}:${{REDIS_PASSWORD}}@${{RAILWAY_PRIVATE_DOMAIN}}:${{REDIS_PRIVATE_PORT}}
and PostGIS should postgres://${{POSTGRES_USER}}:${{POSTGRES_PASSWORD}}@${{RAILWAY_TCP_PROXY_DOMAIN}}:${{RAILWAY_TCP_PROXY_PORT}}/${{POSTGRES_DB}}
Let's try this — could I suggest a PR environment replicated based on your production one, push a test commit (that doesn't change anything material) and we can then wire up the variables and see what we run into? Once you have this up, could you share a link to the PR environment here?
Status changed to Awaiting User Response Railway • 9 months ago
9 months ago
we've got a time with Angelo scheduled for Monday - so I'm going to see if we can resolve this AND the metal migration in one swoop.
To be clear, the two issues were - private URL not resolving AND our metal migration... they may be related.
Thanks!
Status changed to Awaiting Railway Response Railway • 9 months ago
9 months ago
Awesome, in that case going to close this out but please re-open if you run into any issues!
Happy Building
!
Status changed to Awaiting User Response Railway • 9 months ago
Status changed to Solved jpowell • 9 months ago