#Degraded performance after migrating to Metal on Pro Account

140 messages · Page 1 of 1 (latest)

storm surge
#

Hey đź‘‹

We migrated to Metal last week, but we’ve started noticing degraded performance since the switch—quite the opposite of what was expected given all the fuzz and marketing about it. Our project is now using more RAM, CPU, and response times have increased significantly.

I’d appreciate it if we could get proper support on this in a private channel, as I prefer not to share official data or analytics publicly.

Thanks in advance!

patent veldtBOT
#

Project ID: 871738a3-42f1-4feb-89e8-cd361440240e

storm surge
crude elk
#

Given that you’re not on a Pro or Enterprise plan, private team support is not warranted here.

Please provide more details as to what languages/frameworks/tasks your services run. Given that this is a rare report of increased resource usage after switching to metal, it is likely that your services either hit an edge case or your configuration was changed in some way.

storm surge
crude elk
#

Apologies, your discord account does not have the pro role.

#

Raising this to the team

#

!t

humble templeBOT
#

New reply sent from Help Station thread:

⬆️ This thread has been escalated to the Railway team.

You're seeing this because this thread has been automatically linked to the Help Station thread.

storm surge
storm surge
#

Apologies if this comes across as unfair, but we wanted to follow up as it’s been over 24 hours since we initially reached out. On the Pro plan, Railway advertises “Railway Support (1 Business Day),” and we were expecting a response within that timeframe.

Since migrating to Metal, we’ve experienced noticeable performance degradation along with increased resource usage — which will result in higher charges on our end. We’d really appreciate timely assistance to help resolve these issues.

ashen vine
#

Hello,

That time frame applies to threads created on the central station, this thread was created on Discord.

storm surge
#

This thread has been moved to the Central Station more than 24h ago, so the same applies.

ashen vine
#

Unfortunately it doesnt, but please provide real time data here, unfortunately anecdotal evidance is not enough for us to look into.

storm surge
#

I’m genuinely frustrated that, as a paying customer, we’re spending more time debating our Pro status or when a thread was moved to the appropriate channel than actually resolving the underlying issue.

From what’s clearly shown in this very thread, the escalation to the Railway team happened yesterday at 5:17 PM UTC, and it also states that it was automatically linked to the Help Station thread — both of which are visible in the attached messages.

So please clarify: if that’s not enough to move things forward, what is? What exactly is missing from our side to receive the support we’re entitled to?

ashen vine
storm surge
#

As mentioned earlier in this thread, I’m not looking to share this data publicly, as it may contain sensitive information. I’m still waiting for guidance on how to share it privately with Railway only.

ashen vine
#

I've marked the CS thread as private, lets move there.

humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT
humble templeBOT