Max connection issues
I am running into max connection issues when I am using supabase within an application hosted in a serverless environment (vercel).
I've done everything I can find by the docs, but if I have a spike of 300+ users on my app at once, I start to run into a lot of max connection errors.
I am using trpc to help batch request and limit connections made. I create the postgres connection outside of drizzle, set max connections to 3, and pass the instance in. I am using transaction mode in supabase so it uses supavisor. I have prepared statements set to false.
Does anyone have any advice that might be harder to come by? I am not as familiar with serverless environments and am about to pull the plug and move it over to a long-standing server to help my app scale.
Went through this guide as well
https://github.com/orgs/supabase/discussions/22305
Thanks!
I've done everything I can find by the docs, but if I have a spike of 300+ users on my app at once, I start to run into a lot of max connection errors.
I am using trpc to help batch request and limit connections made. I create the postgres connection outside of drizzle, set max connections to 3, and pass the instance in. I am using transaction mode in supabase so it uses supavisor. I have prepared statements set to false.
Does anyone have any advice that might be harder to come by? I am not as familiar with serverless environments and am about to pull the plug and move it over to a long-standing server to help my app scale.
Went through this guide as well
https://github.com/orgs/supabase/discussions/22305
Thanks!
GitHub
Based on comment by Chasers from the Supavisor Team. What causes "Max client connections reached" Errors The amount of connections the Supavisor pooler can support is determined by your d...
