n/a

the project id is very much applicable, along with a service id and environment name

Ok, one moment

2d33fa31-ec9a-4d1c-ad51-95f81d2b8978

what region does the supabase database reside in?

ca-central1

... are you aware your region in railway is us-west?

I was not. Are they supposed to be in the same region?

absolutely, distance really matters for latency, though i am just assuming here because you dont have any tracing

i assume you live somewhere close to the supabase region?

Yes

Is it possible to change the region for our railway?

yeah, change it to east, and then change your supabase region to east as well

Additionally, though latency may be a factor, majority of the time the requests go on pretty fine. Does this really affect why the request lag from time to time?

it looks pretty constantly slow to me?

The transcribes go on okayish. Have never had an issue there

It lags on time to time on the main generations

/api/generator/photosheet was 78 seconds

what are you using to generate?

The python server handles the generation, it takes time depending on the size of the upload, so this is expected. But the lags we face occurred initially with only 3 photos, which never take that long

Eg testing locally with the same photos, it's pretty quick

so you do generation on the cpu?

Ya

doesnt look like whatever you are doing is even using the cpu

we dont have gpus incase you where wondering

The generations just take a bunch of photos and add them to a doc, so I don't think it takes too much compute

try on metal east and supabase east, then we can go from there

Ok

you've already moved supabase?

No. Trying to find focumentation

Will get back to you on this, as it may take me some time

no worries