This is a multi-part message in MIME format.
------_=_NextPart_001_01CB4343.6B86B8F4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
I have pgbouncer running on the same server, and I get over 2000 calls
to a php page per minute.
Each call does inserts data digests into partitioned tables.
I also have a multi-threaded daemon connected to the same database
running background operations on the data coming in.
Works flawlessly.
BTW, 20 connections is not a heavy load at all.
In my application, pgbouncer has opened about 60 backends to handle the
cases where I have a high oncurrency of data coming in at once, but
usually the # non-idle connections is < 10.
=20
=20
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Kieren Scott
Sent: Monday, August 23, 2010 8:38 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pgBouncer for connection pooling
=20
Hi,
I have a web-based application (drupal) which uses PHP to make
connections to a back-end postgresql 8.3 server. The application and
database are on separate servers, but as we can get 20+ concurrent
connections on the database I've looked at pgBouncer to try and reduce
the overhead of new connections on the database. I currently have
pgBouncer running on the same server as my postgres database but I was
wondering whether this is a recommended setup - are the performance
benefits of using a connection pooler overshadowed by the overhead of
running pgBouncer on the same server as the database?
How are other people using pgBouncer? E.g. on a separate server from the
database etc...?
Thanks in advance.
------_=_NextPart_001_01CB4343.6B86B8F4
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
charset=3Dus-ascii">
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>I have pgbouncer running on the same server, and I get =
over 2000
calls to a php page per minute.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>Each call does inserts data digests into partitioned =
tables.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>I also have a multi-threaded daemon connected to the same
database running background operations on the data coming =
in.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>Works flawlessly.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>BTW, 20 connections is not a heavy load at =
all.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>In my application, pgbouncer has opened about 60 backends =
to
handle the cases where I have a high oncurrency of data coming in at =
once, but
usually the # non-idle connections is < 10.
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif" ;
color:#1F497D'>
0in 4.0pt'>
0in 0in 0in'>
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"' >From:=
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"' >
pgsql-admin-owner@postgresql.org =
[mailto:pgsql-admin-owner@postgresql.org] On
Behalf Of Kieren Scott
Sent: Monday, August 23, 2010 8:38 AM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] pgBouncer for connection =
pooling
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"' >Hi,
I have a web-based application (drupal) which uses PHP to make =
connections to a
back-end postgresql 8.3 server. The application and database are on =
separate servers,
but as we can get 20+ concurrent connections on the database I've looked =
at
pgBouncer to try and reduce the overhead of new connections on the =
database. I
currently have pgBouncer running on the same server as my postgres =
database but
I was wondering whether this is a recommended setup - are the =
performance
benefits of using a connection pooler overshadowed by the overhead of =
running
pgBouncer on the same server as the database?
How are other people using pgBouncer? E.g. on a separate server from the
database etc...?
Thanks in advance.