| From: | Kieren Scott <kierenscott(at)hotmail(dot)com> |
|---|---|
| To: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | pgBouncer for connection pooling |
| Date: | 2010-08-23 14:38:14 |
| Message-ID: | BAY149-w45AD2D7EB1BFEF71621197AE820@phx.gbl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2010-08-23 16:02:31 | Re: pgBouncer for connection pooling |
| Previous Message | Scott Marlowe | 2010-08-23 08:23:12 | Re: [GENERAL] getting list of columns from a query |