Supavisor pooler

self-hosted🔢DB Connections

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

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

Supavisor pooler

self-hosted🔢DB Connections

Hello guys

# 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 pooler

Similar Threads

Supavisor pooler

Similar Threads

Similar Threads

Similar Threads