pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pailloncy Jean-Gérard <pailloncy@ifrance.com>
Cc: pgsql-performance@postgresql.org
Subject: Re:
Date: Wed, 14 Apr 2004 09:22:42 -0400
Message-ID: <4923.1081948962@sss.pgh.pa.us> (raw)
In-Reply-To: <C0EA9494-8E10-11D8-BBA5-000A95DE2550@ifrance.com>
References: <C0EA9494-8E10-11D8-BBA5-000A95DE2550@ifrance.com>

=?ISO-8859-1?Q?Pailloncy_Jean-G=E9rard?= <pailloncy@ifrance.com> writes:
> I run the following command three times to prevent cache/disk results.

Do you think that's actually representative of how your database will
behave under load?

If the DB is small enough to be completely cached in RAM, and you
expect it to remain so, then it's sensible to optimize on the basis
of fully-cached test cases.  Otherwise I think you are optimizing
the wrong thing.

If you do want to plan on this basis, you want to set random_page_cost
to 1, make sure effective_cache_size is large, and perhaps increase
the cpu_xxx cost numbers.  (What you're essentially doing here is
reducing the estimated cost of a page fetch relative to CPU effort.)

			regards, tom lane



view thread (4+ messages)  latest in thread

Message-ID: <4923.1081948962@sss.pgh.pa.us>
Permalink:  ../4923.1081948962@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4923.1081948962@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pailloncy@ifrance.com
  Subject: Re:
  In-Reply-To: <4923.1081948962@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