Neon connection limit and AWS lambda


Are there folks using neon with AWS lambda? How has their experience been with the connection limit? It seems that it’s 100 before using pgbouncer and 1000 afterwards. Can the 1000 limit be increased?

What is Neon’s priority when it comes to supporting lambda backends?


Hey! DB concurrent connections is a known bottleneck which is addressed by connections pool. Unfortunately by design lambda runtime virtualization does not permit to share a pool between different lambda instances. The workaround is, to setup a database reverse proxy to manage a connections pool. For example, AWS provides the RDS proxy service to absorb to facilitate the setup for RDS. In the case of Neon, we can think of a community driven OSS solution for the problem :thinking: WDYT folks?

We also increased pgbouncer connection limit to 10k simultaneous connections. Now that is on prod (we’ll follow up with the corresponding docs change).

1 Like

Hm, I think that it is pretty harmless to increase connection limits on our pgbouncer (or as a more long-term project – get built-in postgres connection pooler merged, there is a thread in hackers). Generally connections are some amount of memory and open files.

Or is it somehow beneficial to run some proxy/pooler on AWS side?