Hello,

All Hobby deploys go exclusively to metal now.

Please make sure you are using the private network to avoid latency.

Best,

Brody

ok

previous experiments have shown that connecting through private network wont solve the issue:

https://help.railway.com/questions/slower-performance-since-nov-18th-f139afa8

it'd be reasonable to delay enforcing metal on hobby users until metal supports volumes (for db services)

Are you sure you are connecting to the database via private network?

yes.

connection variable

similar performance impact as reported on the previous thread (linked above)

Are you opening a new database connection for every query?

i dont think so but not sure. i'm using default RubyOnRails 7.2 behaviour.

Please look into that.

it's not a new connection per query

ActiveRecord uses a connection pool. When you try to interact with the database, a connection is acquired from the pool, query is made and connection is returned to pool after the query. All this is handled by ActiveRecord in the background. You can adjust the number of connections in the pool in your database configuration

http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAdapters/ConnectionPool.html

How many queries are you making per API route?

Irrelevant. The point is that without notice railway enforced a new policy that impacts my end-users with over a second (sometimes 2-3 seconds) delay.

Railway has made a habit of this kind of unnoticed changes that impact end users.

Is there an ETA on metal supporting volumes?

Sorry but I am not able to provide one.