From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vincent van Leeuwen <pgsql.spam@vinz.nl>
Cc: pgsql-performance@postgresql.org
Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning
Date: Tue, 10 Jun 2003 15:43:47 -0400
Message-ID: <4332.1055274227@sss.pgh.pa.us> (raw)
In-Reply-To: <20030610181247.GX1535@md2.mediadesign.nl>
References: <EFF9ABB64B24D511A75C0002A5512D5C01911DE4@LEWEXCH>
<200306100846.21875.josh@agliodbs.com>
<20030610181247.GX1535@md2.mediadesign.nl>
Vincent van Leeuwen <pgsql.spam@vinz.nl> writes:
> Halving the cpu_tuple_cost has given a very impressive performance boost
> (performance roughly doubled). I'm not sure why, because the plans of the
> large queries I was checking haven't changed as far as I can see, but maybe
> some smaller queries I didn't bother to check are using a different plan now.
That's very curious; I'd expect that parameter to have only marginal
effect in the first place (unless you make huge changes in it, of course).
It must have changed some plan that you didn't take note of. If you can
find it I'd be interested to know.
> Just to be absolutely sure: all *_cost parameters only influence the
> chosen plan, right? There is absolutely nothing else influenced which
> doesn't show up in an EXPLAIN ANALYZE, right?
AFAIR, the only one of these parameters that the executor pays any
attention to is SORT_MEM; that will determine how soon the runtime code
starts to spill tuples to disk in sorts, hash tables, etc.
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 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: tgl@sss.pgh.pa.us, pgsql.spam@vinz.nl
Subject: Re: FW: [ADMIN] Shared_buffers and kernel parameters, tuning
In-Reply-To: <4332.1055274227@sss.pgh.pa.us>
References: <EFF9ABB64B24D511A75C0002A5512D5C01911DE4@LEWEXCH> <200306100846.21875.josh@agliodbs.com> <20030610181247.GX1535@md2.mediadesign.nl> <4332.1055274227@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