| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | hmidi slim <hmidi(dot)slim2(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pool connection |
| Date: | 2017-12-29 11:53:54 |
| Message-ID: | 20171229115354.GC1458@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Dec 29, 2017 at 11:47:01AM +0100, hmidi slim wrote:
> I'm trying to understand the utility of pool connection, I found that it's
> useful to enhance the performance of a database. However I want to know if
> it is a good option to put a large number in max_connection option to
> handle a large number of connection in an app?
A couple of hundred connections is already a lot as a point of
contention is snapshot build, which is particularly painful for OLTP
workloads. If you reach a point where you need hundreds of connections,
I would recommend using pgbouncer. This will save your server much CPU
by minimizing the effects of connections still around but idle.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marco Nenciarini | 2017-12-29 13:15:22 | [PATCH] Logical decoding of TRUNCATE |
| Previous Message | hmidi slim | 2017-12-29 10:47:01 | pool connection |