Wells Oliver <woliver(at)padres(dot)com> wrote:
> Do you have any recommendations on a pg connection pooler?
If the software you're using includes a connection pool, that is
often the best choice; if not (or it doesn't work well) both pgpool
and pgbouncer have their followings.
In my view the most important things are that the pool have a hard
upper limit on the number of database connections, that it is aware
of database transactions, and that when all connections are busy it
will queue a request to start a new transaction until one of the
existing transactions completes. A good pooler, configured to the
right size (which is usually at or close to the number of actual
cores on the machine, times two), will improve both throughput and
response time under load.
-Kevin