From: Bob Dusek <redusek@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: performance config help
Date: Wed, 13 Jan 2010 15:10:04 -0500
Message-ID: <61039b861001131210j673f1200r16f60f26f5a22265@mail.gmail.com> (raw)
In-Reply-To: <4B4D53BF.4020905@postnewspapers.com.au>
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>
FYI - We have implemented a number of changes...
a) some query and application optimizations
b) connection pool (on the cheap: set max number of clients on
Postgres server and created a blocking wrapper to pg_pconnect that
will block until it gets a connection)
c) moved the application server to a separate box
And, we pretty much doubled our capacity... from approx 40 "requests"
per second to approx 80.
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.
We've also tried third-party connection pools and they don't seem to
be real fast.
Thanks for all of your input. We really appreciate it.
Bob
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: redusek@gmail.com
Subject: Re: performance config help
In-Reply-To: <61039b861001131210j673f1200r16f60f26f5a22265@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