From: Rod Taylor <rbt@sitesell.com>
To: David Parker <dparker@tazznetworks.com>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: time to stop tuning?
Date: Fri, 26 Nov 2004 13:29:19 -0500
Message-ID: <1101493759.44437.302.camel@home> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com>
On Fri, 2004-11-26 at 12:13 -0500, David Parker wrote:
>
> I suspect the ultimate answer to our problem will be:
>
> 1) aggressive client-side caching
> 2) SQL tuning
> 3) more backend hardware
#0 might actually be using connection pooling and using cached query
plans (PREPARE), disabling the statistics daemon, etc.
For the plans, send us EXPLAIN ANALYZE output for each of the common
queries.
If you can try it, I'd give a try at FreeBSD or a newer Linux on your
system instead of Solaris. Older versions of Solaris had not received
the same amount of attention for Intel hardware as the BSDs and Linux
have and I would imagine (having not tested it recently) that this is
still true for 32bit Intel.
Another interesting test might be to limit the number of simultaneous
connections to 8 instead of 30 (client side connection retry) after
client side connection pooling via pgpool or similar has been installed.
Please report back with your findings.
--
Rod Taylor <rbt@sitesell.com>
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: rbt@sitesell.com, dparker@tazznetworks.com
Subject: Re: time to stop tuning?
In-Reply-To: <1101493759.44437.302.camel@home>
* 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