From: Kieren Scott <kierenscott@hotmail.com>
To: pgsql-admin@postgresql.org
Subject: pgBouncer for connection pooling
Date: Mon, 23 Aug 2010 14:38:14 +0000
Message-ID: <BAY149-w45AD2D7EB1BFEF71621197AE820@phx.gbl> (raw)
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.
=
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kierenscott@hotmail.com
Subject: Re: pgBouncer for connection pooling
In-Reply-To: <BAY149-w45AD2D7EB1BFEF71621197AE820@phx.gbl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox