pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Craig Ringer <craig@postnewspapers.com.au>
To: Bob Dusek <redusek@gmail.com>
Cc: Scott Marlowe <scott.marlowe@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance config help
Date: Thu, 14 Jan 2010 13:47:13 +0800
Message-ID: <4B4EAFE1.4050909@postnewspapers.com.au> (raw)
In-Reply-To: <61039b861001131437j4a70ab8nd68ebf0733994854@mail.gmail.com>
References: <4B4B177B020000250002E194@gw.wicourts.gov>
	<dcc563d11001111136y117ea68dp651fd24ce72385f3@mail.gmail.com>
	<4B4B3BF6020000250002E1B1@gw.wicourts.gov>
	<61039b861001111323g531a5d68q1f59171d926aefef@mail.gmail.com>
	<alpine.DEB.2.00.1001121641360.25000@aragorn.flymine.org>
	<61039b861001121001p37dc7698i48651189edcee9d0@mail.gmail.com>
	<4B4D53BF.4020905@postnewspapers.com.au>
	<61039b861001131210j673f1200r16f60f26f5a22265@mail.gmail.com>
	<dcc563d11001131243l1a53c485s452780f9f6abb976@mail.gmail.com>
	<61039b861001131437j4a70ab8nd68ebf0733994854@mail.gmail.com>

Bob Dusek wrote:
>>> The problem with our "cheap" connection pool is that the persistent
>>> connections don't seem to be available immediately after they're
>>> released by the previous process.   pg_close doesn't seem to help the
>>> situation.  We understand that pg_close doesn't really close a
>>> persistent connection, but we were hoping that it would cleanly
>>> release it for another client to use.  Curious.
>> Yeah, the persistent connects in php are kinda as dangerous as they
>> are useful..  Have you tried using regular connects just to compare
>> performance?  On Linux they're not too bad, but on Windows (the pg
>> server that is) it's pretty horrible performance-wise.
> 
> Yes we have.  Regular connections are pretty slow, even when our
> application server is on the same box as the db server.
> 
>>> We've also tried third-party connection pools and they don't seem to
>>> be real fast.
>> What have you tried?  Would pgbouncer work for you?
> 
> We've tried pgbouncer.  It's pretty good.

Oh, also look into mod_dbd . With the threaded MPM it can apparently
provide excellent in-apache connection pooling.

--
Craig Ringer




view thread (46+ messages)  latest in thread

Message-ID: <4B4EAFE1.4050909@postnewspapers.com.au>
Permalink:  ../4B4EAFE1.4050909@postnewspapers.com.au/
Also on:    postgresql.org/message-id/4B4EAFE1.4050909@postnewspapers.com.au

 · 

reply
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-performance@postgresql.org
  Cc: craig@postnewspapers.com.au, redusek@gmail.com, scott.marlowe@gmail.com
  Subject: Re: performance config help
  In-Reply-To: <4B4EAFE1.4050909@postnewspapers.com.au>

* 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