Supavisor: Scaling Postgres to 1M Connections(supabase.com) |
Supavisor: Scaling Postgres to 1M Connections(supabase.com) |
this was a very fun load test to run. happy to answer any questions.
shoutout to José Valim and the Dashbit team for the help on Supavisor. elixir and erlang are amazing tools.
connection limits, even with pgbouncer, have been a big support burden for us. supavisor should let us be more liberal with connections we allot to folks.
supavisor is rolled out and available for all projects to use today. contact support[0] and we can expose the supavisor connection string in your dashboard. we'll be proactively exposing it to everyone gradually over the next ~1 month. we'll run pgbouncer and supavisor both for you for probably ~5 months before you need to switch to supavisor.
also very excited at the potential features a custom postgres proxy can unlock.
another 1ms goes for a gain of a millions connections, multitenancy, and a lot of features that are possible to implement and are planned to implement.
i am curious what usecase do you have, that 2ms is unacceptable? in most cases it would be insignificant to network latency to the end client
would be happy to answer questions about load testing setup
here is the github repo[0] with an app that helps me launch terraforms and k6 and keep track of launches/results