From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Parker <dparker@tazznetworks.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: time to stop tuning?
Date: Fri, 26 Nov 2004 14:04:35 -0500
Message-ID: <10504.1101495875@sss.pgh.pa.us> (raw)
In-Reply-To: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com>
References: <07FDEE0ED7455A48AC42AC2070EDFF7C26BDD2@corpsrv2.tazznetworks.com>
"David Parker" <dparker@tazznetworks.com> writes:
> 1) Given that the data is all cached, what can we do to make sure that
> postgres is generating the most efficient plans in this case? We have
> bumped up effective_cache_size, but it had no effect.
If you're willing to bet on everything being in RAM all the time,
dropping random_page_cost to 1 would be a theoretically sound thing
to do. In any case you should look at reducing it considerably from
the default setting of 4.
Something that might also be interesting is to try increasing all the
cpu_xxx cost factors, on the theory that since the unit of measurement
(1 sequential page fetch) relates to an action involving no actual I/O,
the relative costs of invoking an operator, etc, should be rated higher
than when you expect actual I/O. I'm not real confident that this would
make things better --- you might find that any improvement would be
swamped by the low accuracy with which we model CPU costs (such as the
assumption that every operator costs the same to evaluate). But it's
worth some experimentation.
regards, tom lane
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: tgl@sss.pgh.pa.us, dparker@tazznetworks.com
Subject: Re: time to stop tuning?
In-Reply-To: <10504.1101495875@sss.pgh.pa.us>
* 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