pgBouncer for connection pooling
am 23.08.2010 16:38:14 von Kieren Scott--_d16c902b-344d-418a-a65c-5be5b6b1d768_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi=2C
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 se=
parate servers=2C but as we can get 20+ concurrent connections on the datab=
ase I've looked at pgBouncer to try and reduce the overhead of new connecti=
ons 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 s=
etup - are the performance benefits of using a connection pooler overshadow=
ed 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 da=
tabase etc...?
Thanks in advance.
=
--_d16c902b-344d-418a-a65c-5be5b6b1d768_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi=2C
I have a web-based application (drupal) which uses PHP to make=
connections to a back-end postgresql 8.3 server. The application and datab=
ase are on separate servers=2C 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 pool=
er overshadowed by the overhead of running pgBouncer on the same server as =
the database?
How are other people using pgBouncer? E.g. on a separa=
te server from the database etc...?
Thanks in advance.
=
=
--_d16c902b-344d-418a-a65c-5be5b6b1d768_--