Re: Connection pooling - Number of connections

From: Tom Lane
Subject: Re: Connection pooling - Number of connections
Date: ,
Msg-id: 18360.1395418662@sss.pgh.pa.us
(view: Whole thread, Raw)
In response to: Re: Connection pooling - Number of connections  (Guillaume Smet)
Responses: Re: Connection pooling - Number of connections  (Sethu Prasad)
Re: Connection pooling - Number of connections  (Guillaume Smet)
List: pgsql-performance

Tree view

Connection pooling - Number of connections  (Guillaume Smet, )
 Re: Connection pooling - Number of connections  (David Johnston, )
  Re: Connection pooling - Number of connections  (Guillaume Smet, )
   Re: Connection pooling - Number of connections  (Tom Lane, )
    Re: Connection pooling - Number of connections  (Sethu Prasad, )
     Re: Connection pooling - Number of connections  (Guillaume Smet, )
     Re: Connection pooling - Number of connections  (David Johnston, )
    Re: Connection pooling - Number of connections  (Guillaume Smet, )
     Re: Connection pooling - Number of connections  (Claudio Freire, )
      Re: Connection pooling - Number of connections  (Brett Wooldridge, )

Guillaume Smet <> writes:
> On Fri, Mar 21, 2014 at 4:49 PM, David Johnston <> 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...

It will cost you, in ProcArray scans for example.  But lots-of-idle-
connections is exactly what a pooler is supposed to prevent.  If you have
a server that can handle say 10 active queries, you should have a pool
size of 10, not 100.  (If you have a server that can actually handle
100 active queries, I'd like to have your IT budget.)

The proposed design sounds fairly reasonable to me, as long as users are
clear on how to set the pool size --- and in particular that bigger is
not better.  Clueless users could definitely shoot themselves in the
foot, though.

            regards, tom lane



pgsql-performance by date:

From: Shaun Thomas
Date:
Subject: Re: Getting query plan alternatives from query planner?
From: Erik van Zijst
Date:
Subject: Suboptimal query plan when using expensive BCRYPT functions