a year ago
Hi Railway team,
I'm hosting a Django app on Railway and I've noticed that my response times are consistently higher due to queuetime.
My app’s total response time is around 150–160ms.
When I exclude queuetime, the actual Django processing time is only 45–55ms.
This suggests that about 100ms is being spent before the request even reaches my app. I’m on the hobby tier, and this happens even with very low traffic, so I’m wondering if this might be due to cold starts, concurrency limits, or something in the platform routing layer.
A few questions:
Is this kind of queuetime expected on my current tier?
Would moving to a higher plan or enabling “always-on” reduce this delay?
Is there anything else I can do to improve the latency?
Appreciate your help, and I’m happy to share logs or metrics if needed. Thanks!
1 Replies
a year ago
Hello,
We don't do any response queuing of any kind, on any plan, unless you have serverless on, but you don't.
It looks like the majority of requests made to the application enter via our EU-West Edge region, but the service itself is located in US-West, so it's highly likely the time you are perceiving as queue time is simply the little trip around the world that your requests are doing.
Please move both the database and application to the region closest to yourself and let me know if the queue time decreases.
You will also need to connect to the database via the private network.
Best,
Brody
Status changed to Awaiting User Response Railway • 11 months ago
7 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 • 7 months ago