I use database sessions and the first query to get the session is about 500ms

It’s 1ms on local dev

2d107d26-eef1-44e4-9d3b-ef006de2f025

Is this a connection thing? I think it might be your connection to the internet? I had the sme thing

Nope I have 1gb internet and no issues when deploying on Laravel forge with a cheap hetzner droplet

Might be the Database your using and the processing that it requires?

I just spun up a MySQL db on railway

400ms for a single from lookup. Vs 1ms on local

Not sure what else I can do setup wise on railway to aid

I got told that Postgres is the most lightweight on railway

Whats the reason why this delay matters?

Local vs production.

I don’t have my benchmark from forge/hetzner but even that was much faster compared to railway setup thus far

when you say production, does that mean your application running on Railway?

Yes sorry I mean the issue with speeds is solely when using railway

Local is very fast ( not expecting local speeds)

Laravel forge using the cheapest hetzner droplet is very fast.

Railways is very slow in comparison.

I don’t think I have configured anything incorrectly but I’m open to suggestions

But for the same query request on local it’s 1ms vs 300-400ms on railway. Seems quite a steep increase

Pictures above for comparison

are you opening a new database connection for every db call?

Nope. Well it’s just standard php Laravel app.

is both your application and database on metal?

Yes both on metal and both same region. Spun up yesterday. Used railpack as per one of your YouTube videos on setting up a Laravel app

It seems like the first query of each request is always the slowest by far

can you provide some full traces?

Not sure if this is what you are after but here goes. As you can see the first db call is by far the longest for what is a single record return. I turned off datbase sessions which was orignally top of the list, now that was removed this is the first in the list and now much higher.

yeah it looks like you are establishing a connection for every route, you would want to have a global connection pool