a year ago
It might be faster with aws than railway.
I didn't face same situation when I use aws even freetier.
But I am not sure it's usual situation or I have some issue?
I am staying east asia and building service with django and postgresql.
7 Replies
Status changed to Awaiting User Response Railway • 12 months ago
a year ago
Yeah. I tried to change region to south east asia(Singapore Metal).
But it makes slower then US west(Non metal)
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
Next step would be running gunicorn with the uvicorn event worker to rule out single threaded issues.
Status changed to Awaiting User Response Railway • 12 months ago
brody
Next step would be running gunicorn with the uvicorn event worker to rule out single threaded issues.
a year ago
I tried as you said running django app with uvicorn.
As I expected, it made same performance.
I don't think the response time slow issue is related to backend thread issues.
Because my family only use this service.
There are not much requests.
I guess it's more related network system with railway server located.
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
I'm not sure if even the distance can account for that, this is seeming more like a code bottleneck.
I would recommend adding tracing to your application code in order to find out where that slowness actually comes from.
Status changed to Awaiting User Response Railway • 12 months ago
brody
I'm not sure if even the distance can account for that, this is seeming more like a code bottleneck.I would recommend adding tracing to your application code in order to find out where that slowness actually comes from.
a year ago
I already test it with django debug toolbar.
I am convinced it's not the issue related code level.
It's more related to infrastructure in railway.
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
Hello,
After some investigating, I've confirmed that our platform infrastructure is functioning normally in the region your application has been deployed to, and the region you are accessing the application from. I've specifically checked the average response times for all deployments on the same host and that originated from the same region as your requests do, and your application is the only one experiencing elevated response times, which confirms this is an application-level issue rather than a platform issue.
Some common causes for Django slowdowns include middleware configuration issues or connections to slow and or distant third-party APIs. You might want to check these areas first during your debugging process.
As Railway's support is limited to platform-related issues, and this issue is within your application layer, I'll need to close this support ticket at this time.
If you have a specific platform-related question during your investigation, please feel free to open a new ticket with those details.
Best of luck with your debugging, and thank you for using Railway.
Best,
Brody
Status changed to Awaiting User Response Railway • 12 months ago
Status changed to Closed brody • 12 months ago