Intentionally slow databases in free tier?
I'm trying out railway for our web app and must say I feel like the database is intentionally very slow to execute simple queries that returns no rows. Is this intentionally slow so as not to hog up resources in free tier? Can I expect better performance in Enterprise?
It takes 150ms to execute this query that returns nothing. Compared to my local database that does this in 2-3 ms. And that's me running on a weak laptop π
11 Replies
Project ID:
N/AN/A
If you are on the hobby plan, all your deployments are in us-west-1, so, depending on where you are located, you could be running into latency issues.
But the fetching is at 9ms, the execution happens on the server.
riiight?? or no?
I missed that part. My bad. I donβt think itβs intentionally slowed down though
Alright, it also seems to crash now and then because when deploying my api it says
In case any railway employee sees this, my project id is
c39b75c1-5e52-4d8e-b559-4cc3d1c83383.Can't reach database server atthis can be caused by the private network initialization times, even if you arent using the private network, its enabled by default, the fix being disable the private network or increase the connection timeout, and in some edge cases a retry loop may be neededcontainers-us-west-120.railway.app:7756
Hmm okay, I will try to diaable it tomorrow. I also tested with a database hosted outside of railway. Bpth these works sometimes, and sometimes not.. so it must be what u say with some weird timeout.
Unfortunately it seems I'll have to go with an external postgres because the postgres performance are for some reason unreasonably slow. I think it mist be misconfigured or smth
I hoped upgrading to a pro plan would do the trick π
can you do me a favor and test this database?
https://railway.app/template/postgres
Equally slow π¦
That did it, now my service seems to be able to connect to the db(my external) every restart.
it's very odd that it's so slow, it's just a postgres docker image, nothing fancy at all