Poor performance

I've migrated a project from heroku's basic dyno (capped at 500Mb RAM) to railway and I saw a great difference in performance. Is this to be expected? Project ID is 02153a9e-0961-4df0-973f-a3d3ded857f4
13 Replies
angelo
angelo2y ago
Unfortunately yes because of the region, Us-West only. Where was your dyno located before?
dwaynemac
dwaynemac2y ago
heroku doesnt give option. I believe their location is us-east-1
angelo
angelo2y ago
Yep, I am going to tag in @char8 just for this records when he is awake. But I think it will be that + our proxy. Are you in Argentina?
dwaynemac
dwaynemac2y ago
I'm on argentina, yes
angelo
angelo2y ago
Yep, US-East would be faster
dwaynemac
dwaynemac2y ago
My users are mostly on argentina and brasil, also europe
angelo
angelo2y ago
Gotcha, yep, US-East would solve most of your issues. But a BR region would be best. The shot-term solution would be setting up cloudflare for the CDN.
dwaynemac
dwaynemac2y ago
The site is not heavy on assets, don't know if CDN would solve much ok, i've rolled back to heroku. I'll try again this projects migration when regions are available. other projects I migrated didn't seem to receive such an impact
angelo
angelo2y ago
It could have been the host. Can you trigger a redeploy? Really curious to see the latency behavior.
dwaynemac
dwaynemac2y ago
Sure, I'm redeploying now (ruby deploy time is above 10 minutes 👀)
dwaynemac
dwaynemac2y ago
still a big difference in response time between the heroku host and the railway host.
angelo
angelo2y ago
Alright, just what we needed. You can tear it down, in the meantime, I will wait for Charith to report back on what may be the cause for this.
dwaynemac
dwaynemac2y ago
thanks!