Is there anyway to not have supabse project totally brick when we run out of RAM?
Whenever we've run out of RAM on our project the whole project goes into an unhealthy state and our production website goes down and we have to manually reset the project. Our users get very upset. Is this the desired behavior?
6 Replies
Upgrade to a pro plan, get a bigger compute size with more RAM.
Thats what we did, I just wish the whole project didn't freeze when we hit the limit,
Normally it should start slowing down and getting errors before it locks up. I don't know the threshold (75% or similar?) that it would be time to upgrade before it happens. Certainly making sure you queries are tuned, or looking into what pushes you over the top, if not just shear number of users growing.
Yeah all of that makes perfect sense, again I just wish the whole project didn't die when something pushed it over the limit. Granted I have no idea how things work under the hood, but I feel like whatever process pushed it over the limit should error out and auth (for example) can still work. Because right now one bad SQL query can literally bring down an entire project
It is a postgres thing, probably info out there on what to watch for.
I've not dealt with memory limits, but my past projects grew pretty slowly.
You can have a look at Performance Advisor and Query Performance to see which queries are taking the longest and can lead to you running out of memory. You can try to optimise the queries and also see which ones don't necessarily need to happen instantly and background them instead.