> Subject: Re: [ADMIN] pgBouncer for connection pooling > From: jd@commandprompt.com > To: kierenscott@hotmail.com > CC: pgsql-admin@postgresql.org > Date: Mon, 23 Aug 2010 09:02:31 -0700 > > On Mon, 2010-08-23 at 14:38 +0000, Kieren Scott wrote: > > 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...? > > We use it in both on separate boxes as well as local. As long as your > machine is handling the connection processing of the pooler fine, I > wouldn't worry about it. There are some specific high end off machine > things you can do (point at different databases on different machines > from a single pooler) that is cool but for just a Drupal website it is > probably not required. > > JD > > -- > PostgreSQL.org Major Contributor > Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579 > Consulting, Training, Support, Custom Development, Engineering > http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin
