From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
---|---|
To: | David Johnston <polobo(at)yahoo(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Connection pooling - Number of connections |
Date: | 2014-03-21 16:05:03 |
Message-ID: | CALt0+o-W_rTy2M+5rHb61KksSBrCncOT_4=ctf3e_MKYTTVTdA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, Mar 21, 2014 at 4:49 PM, David Johnston <polobo(at)yahoo(dot)com> wrote:
> Consider this train-of-thought: no matter how large the pool size if you
> are constantly keeping, say, 90% of the connections actively working then
> having, on average, 10% of the connections sitting idle is probably not
> going to be noticeable on the server and the reduction in overhead of
> managing a pool is typically a net positive. Now, I had no clue what
> percentage is actually true, or under what conditions and pool sizes it may
> vary, but that is a calculation that someone deciding on between managed and
> un-managed pools would need to make.
Sure.
The big question is if it is suited for general purpose or if having
100 connections open when 10 only are necessary at the time is causing
any unnecessary contention/spinlock issues/performance
overhead/whatever...
--
Guillaume
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-03-21 16:17:42 | Re: Connection pooling - Number of connections |
Previous Message | David Johnston | 2014-03-21 15:49:43 | Re: Connection pooling - Number of connections |