pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Bob Dusek <redusek@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: performance config help
Date: Wed, 13 Jan 2010 13:43:29 -0700
Message-ID: <dcc563d11001131243l1a53c485s452780f9f6abb976@mail.gmail.com> (raw)
In-Reply-To: <61039b861001131210j673f1200r16f60f26f5a22265@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>

On Wed, Jan 13, 2010 at 1:10 PM, Bob Dusek <redusek@gmail.com> wrote:
> And, we pretty much doubled our capacity... from approx 40 "requests"
> per second to approx 80.

Excellent!

> 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.

> 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?



view thread (46+ messages)  latest in thread

Message-ID: <dcc563d11001131243l1a53c485s452780f9f6abb976@mail.gmail.com>
Permalink:  ../dcc563d11001131243l1a53c485s452780f9f6abb976@mail.gmail.com/
Also on:    postgresql.org/message-id/dcc563d11001131243l1a53c485s452780f9f6abb976@mail.gmail.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: scott.marlowe@gmail.com, redusek@gmail.com
  Subject: Re: performance config help
  In-Reply-To: <dcc563d11001131243l1a53c485s452780f9f6abb976@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>

* 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