3 days ago
Hello, I'm developing a SaaS application hosted on Vercel. For testing purposes, I decided to use Railway's free plan and was so satisfied with the query speed that after the trial ended today, I upgraded to the Pro plan to run final tests before going into production.
Unfortunately, since upgrading, the latency has become ridiculous. I'm seeing delays of 4-10 seconds for simple queries that return just a few records, using the exact same schema as before.
To rule out Vercel as the problem, I tried connecting from my local machine and the problem persists.
Has anyone else experienced something similar?
1 Replies
3 days ago
What vercel region are you using?
Washington DC USA (East). But as I said, the same happens when I connect to railway running the project locally from Argentina.
Also tried to erase everything in railway and set it up from the start, changing regions, etc, but the results were the same
3 days ago
Can you share some example queries?
To be honest I was asking mostly because maybe I needed to do some aditional configurations after upgrading to the pro plan. I have been testing the app with vercel and railway for a month with no problems.
3 days ago
Uh, that is a massive query. You may want to optimize that.
1 - I was using the free trial from railway, everything worked just fine. Tested everything for about a month.
2 - Free trial ended. Susbcribed to Pro plan.
3 - Latency went nuts without changing anything else.
2 days ago
Nothing has changed on our side, and even the free tier uses the exact same hardware as the pro tier, so it's nothing to do with the upgrade.
Test 1:
Auth (newSession): 2.513ms
findUnique Paciente (newSession): 10.967ms
create Sesion (newSession): 1.045s
newSession Completo: 1.059s
Test 2:
Auth (newSession): 2.214ms
findUnique Paciente (newSession): 6.155ms
create Sesion (newSession): 56.565ms
newSession Completo: 65.456ms
Test 3:
Auth (newSession): 1.966ms
findUnique Paciente (newSession): 8.555ms
create Sesion (newSession): 6.934s
newSession Completo: 6.945s
those are the response times that im getting with vercel hosted in washington dc and railway in virginia.
the 3 tests were made executing the same function wich only makes a small new registry in one of my tables. I got latency as high as 1 minute in other tests, and it ALWAYS have to to with write actions. I tried deploying the DB in california, and while the average latency is much higher, it is stable (always around 500ms)
My point is that the problem are not my queries, it is the hosting in virginia. And since is the optimal location for my app, I need to know if the service is always gone work that way to cancel my subscription and look for another provider.
2 days ago
Hello,
Going to close this out in favour of your existing thread, going forward please try not open duplicate threads.
Status changed to Closed brody • 1 day ago