Postgres Container Memory Limits Question
Howdy y'all. I need some clarification on how database scaling / memory limits work within railway.
I have had my memory usage hit 450mb a couple of times and been unable to access my website or connect to the db while memory usage was high.
What if is any is the scaling behavior of v2 databases on railway (specifically a postgres default instance)? When this has happened to me in the past the only way to fix it was to reboot the container. Just trying to plan appropriately since I know my apps usage is going to spike in the near term as we continue to grow our platform.
https://railway.app/project/3644e3a1-b748-46b4-b196-2a94c381d1f0/service/bf6524db-d1f2-41ee-953b-55cba9112421/metrics
Railway
404 - Page not found
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
7 Replies
Project ID:
3644e3a1-b748-46b4-b196-2a94c381d1f0,bf6524db-d1f2-41ee-953b-55cba9112421Railway services always have full access to the memory/cpu allocated by their plan. If you are on the hobby plan, you will have 8GB RAM to use.
it’s odd that your app slows down when hitting 450mb, have you restarted/redeployed the app since you upgraded to hobby plan?
Yes!
will keep an eye on this
I don't think there is anything we can do until we run up against these limits again and just see what happens 🤔
Just trying to be proactive so that we can handle the hug of death in the future haha
Agreed, there are no logs correct?
No, this was a couple of days ago I am just following up now
It just said something akin to
Cant reach your db at "dburl" too many connections
Got it. Yeah let’s revisit this when it happens again
We only connect to this db via a nextjs app deployed to vercel
prisma under the hood
Thanks adam 🙇♂️ 🫶