Supavisor pooler

Hello guys

I've already done some research but I'm still very confused on how to handle this issue.
I just developed load tests for my app and I start getting timeouts once the tests reach 400 VUs.
The bottleneck is not the server where I'm hosting supabase but is the amount of connection the pooler handles. The server never passes 40% CPU during load tests.

I changed the supavisor config for this:

############
# Supavisor -- Database pooler
############
# Port Supavisor listens on for transaction pooling connections
POOLER_PROXY_PORT_TRANSACTION=6543
# Maximum number of PostgreSQL connections Supavisor opens per pool
POOLER_DEFAULT_POOL_SIZE=75
# Maximum number of client connections Supavisor accepts per pool
POOLER_MAX_CLIENT_CONN=2000
# Pool size for internal metadata storage used by Supavisor
# This is separate from client connections and used only by Supavisor itself
POOLER_DB_POOL_SIZE=5

############
# Supavisor -- Database pooler
############
# Port Supavisor listens on for transaction pooling connections
POOLER_PROXY_PORT_TRANSACTION=6543
# Maximum number of PostgreSQL connections Supavisor opens per pool
POOLER_DEFAULT_POOL_SIZE=75
# Maximum number of client connections Supavisor accepts per pool
POOLER_MAX_CLIENT_CONN=2000
# Pool size for internal metadata storage used by Supavisor
# This is separate from client connections and used only by Supavisor itself
POOLER_DB_POOL_SIZE=5

############
# Supavisor -- Database pooler
############
# Port Supavisor listens on for transaction pooling connections
POOLER_PROXY_PORT_TRANSACTION=6543
# Maximum number of PostgreSQL connections Supavisor opens per pool
POOLER_DEFAULT_POOL_SIZE=75
# Maximum number of client connections Supavisor accepts per pool
POOLER_MAX_CLIENT_CONN=2000
# Pool size for internal metadata storage used by Supavisor
# This is separate from client connections and used only by Supavisor itself
POOLER_DB_POOL_SIZE=5

############
# Supavisor -- Database pooler
############
# Port Supavisor listens on for transaction pooling connections
POOLER_PROXY_PORT_TRANSACTION=6543
# Maximum number of PostgreSQL connections Supavisor opens per pool
POOLER_DEFAULT_POOL_SIZE=75
# Maximum number of client connections Supavisor accepts per pool
POOLER_MAX_CLIENT_CONN=2000
# Pool size for internal metadata storage used by Supavisor
# This is separate from client connections and used only by Supavisor itself
POOLER_DB_POOL_SIZE=5

It seems like it is still very low but I don't know what is reasonable for my server (Hostinger KVM2).

I would like to better understand how are these issues handled with supabase on apps with thousands of users.

Thank you guys

inder•12/20/25, 6:46 PM

My guess is that you're running out of postgres connections. By default in supabase/postgres image max_connections = 100.
When you start to see timeouts, go to Database > roles in studio and see how many connections are active.

ElPutoOP•12/20/25, 7:29 PM

but isn't those connections configured by the POOLER_MAX_CLIENT_CONNPOOLER_MAX_CLIENT_CONN env variable?

ElPutoOP•12/20/25, 7:31 PM

how is it possible that I have 41 admin connections?

EElPuto how is it possible that I have 41 admin connections? 🤔

inder•12/20/25, 7:46 PM

realtime, analytics, supavisor connect as supabase_admin

EElPuto but isn't those connections configured by the `POOLER_MAX_CLIENT_CONN` env varia...

inder•12/20/25, 7:47 PM

This is connections made to supavisor. supavisor still has to make connection to postgres and by default supabase/postgres has 100 connections set

inder•12/20/25, 7:47 PM

You can see that in your screenshot
46/100

inder•12/20/25, 7:50 PM

Here is some more info on these env vars and what they do: https://github.com/supabase/supavisor/issues/595#issuecomment-2955297353

ElPutoOP•12/20/25, 8:17 PM

thanks but for me it's still confusing on can I prevent request timeouts and how can I increase the number of possible concurrent requests

ElPutoOP•12/20/25, 8:17 PM

without overkilling the server

EElPuto thanks but for me it's still confusing on can I prevent request timeouts and how...

inder•12/20/25, 8:43 PM

What are you testing? Rest api or db connections?

inder•12/20/25, 8:43 PM

Can you also share your test workflow

ElPutoOP•12/20/25, 9:25 PM

Im not on the PC right now but I’m doing load tests simulating user flows, like signing in, creating records, calling supabase functions, requesting data, etc. I’m going this with k6 and yes I’m calling supabase with rest api

Supavisor pooler

Similar Threads

Similar Threads

Similar Threads