building time is taking too much. WAY TOO MUCH !!!
mohab9915
PROOP

a month ago

I have three workspaces, each costing between $20 and $220 per month. Recently, deployment build times have become way too long. It used to take under a minute, but now even in the best cases it takes 3–4 minutes. And if I change the requirements and it has to rebuild from scratch, it takes ONE HOUR.

This is extremely frustrating. The time loss is literally costing me money, and it feels like Railway isn’t doing anything about it. I honestly can’t see how Railway is built to scale if this is the experience.

Attachments

Solved

1 Replies

a month ago

Build cache isn't guaranteed on Railway because the build system scales elastically, so your build may land on a node without your previous cache. When cache is missed and your requirements.txt changes, the full dependency tree must be reinstalled. Your services are pulling heavy AI packages which are inherently slow to download and install - this is the source of the hour-long builds. To get consistent fast builds, you'll need to build your own Docker images externally and deploy them directly, or optimize your dependencies.


Status changed to Awaiting User Response Railway 27 days ago


Railway
BOT

20 days 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 20 days ago


Loading...