pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jesper Krogh <jesper@krogh.cc>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: planner costs in "warm cache" tests
Date: Mon, 31 May 2010 20:48:40 +0200
Message-ID: <4C040488.30906@krogh.cc> (raw)
In-Reply-To: <14644.1275244491@sss.pgh.pa.us>
References: <4C02A342.40801@krogh.cc>
	<14644.1275244491@sss.pgh.pa.us>

On 2010-05-30 20:34, Tom Lane wrote:
> Jesper Krogh<jesper@krogh.cc>  writes:
>    
>> testdb=# set seq_page_cost = 0.00001;
>> SET
>> testdb=# set random_page_cost = 0.00001;
>> SET
>>      
> Well, hmm, I really doubt that that represents reality either.  A page
> access is by no means "free" even when the page is already in cache.
> I don't recall anyone suggesting that you set these numbers to less
> than perhaps 0.01.
>
>    
Thank you for the prompt response. Is it a "false assumption" that the
cost should in some metric between different plans be a measurement
of actual run-time in a dead-disk run?

It should most likely be matching a typical workload situation, but that
it really hard to tell anything about, so my "feeling" would be that the
dead disk case is the one closest?

-- 
Jesper



view thread (7+ messages)  latest in thread

Message-ID: <4C040488.30906@krogh.cc>
Permalink:  ../4C040488.30906@krogh.cc/
Also on:    postgresql.org/message-id/4C040488.30906@krogh.cc

 · 

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: jesper@krogh.cc, tgl@sss.pgh.pa.us
  Subject: Re: planner costs in "warm cache" tests
  In-Reply-To: <4C040488.30906@krogh.cc>

* 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