Deployment performance issues / Sluggish load times after upgrading from Free to Hobby plan
kram47172
HOBBYOP

2 months ago

Hi Support Team,

I am opening this ticket because I have noticed that my deployed website is experiencing severe performance issues and slow loading times.

Initially, I assumed this sluggishness was due to the limitations of the Free plan, which is why I decided to upgrade to the Hobby plan. However, even after the upgrade, the website remains just as slow.

I would like to know:

Is there a replication or propagation delay before the performance and resource improvements of the Hobby plan take effect on my deployment?

Are there any specific infrastructure limitations or configurations on my current project that I need to adjust manually to see an improvement?

I would highly appreciate it if you could look into this or provide some guidance to help me identify the root cause of this latency.

Thank you for your time and assistance.

Best regards,

$10 Bounty

2 Replies

Status changed to Awaiting Railway Response Railway about 2 months ago


Railway
BOT

2 months ago

There is no propagation delay - Hobby plan resources apply immediately upon upgrade. The most likely cause of the sluggishness is that App Sleeping (Serverless) is still enabled on your service. On the Free plan, App Sleeping is mandatory, and upgrading to Hobby does not automatically disable it. When App Sleeping is on, your service shuts down after inactivity and the first incoming request triggers a cold start, causing a noticeable delay. You can disable it in your service's Settings > Deploy > Serverless toggle, then redeploy.


Status changed to Awaiting User Response Railway about 2 months ago


Railway

There is no propagation delay - Hobby plan resources apply immediately upon upgrade. The most likely cause of the sluggishness is that App Sleeping (Serverless) is still enabled on your service. On the Free plan, App Sleeping is mandatory, and upgrading to Hobby does not automatically disable it. When App Sleeping is on, your service shuts down after inactivity and the first incoming request triggers a cold start, causing a noticeable delay. You can disable it in your service's Settings > Deploy > Serverless toggle, then redeploy.

kram47172
HOBBYOP

2 months ago

Regards,

I reviewed the configuration and identified that the option is disabled.

image.png

I will proceed to redeploy the project on both the application server and the MySQL server. Once the process is complete and the necessary validations have been performed, I will get back to you with my comments and results.

Best regards.

Attachments


Status changed to Awaiting User Response Railway about 2 months ago


Status changed to Awaiting Railway Response Railway about 2 months ago


Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...