pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gregory Stark <gsstark@mit.edu>
To: pgsql-performance@postgresql.org
Subject: Re: cpu_tuple_cost
Date: 15 Mar 2005 00:30:41 -0500
Message-ID: <87psy1mq66.fsf@stark.xeocode.com> (raw)


Bruce Momjian <pgman@candle.pha.pa.us> wrote:

> Agreed.  I think we should reduce it at least to 3.

Note that changing it from 4 to 3 or even 2 is unlikely to really change much.
Many of the plans people complain about turn out to have critical points
closer to 1.2 or 1.1. 

The only reason things work out better with such low values is because people
have data sets that fit more or less entirely in RAM. So values close to 1 or
even equal to 1 actually represent the reality.

The "this day and age" argument isn't very convincing. Hard drive capacity
growth has far outstripped hard drive seek time and bandwidth improvements.
Random access has more penalty than ever.

-- 
greg




view thread (20+ messages)  latest in thread

Message-ID: <87psy1mq66.fsf@stark.xeocode.com>
Permalink:  ../87psy1mq66.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/87psy1mq66.fsf@stark.xeocode.com

 · 

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: gsstark@mit.edu
  Subject: Re: cpu_tuple_cost
  In-Reply-To: <87psy1mq66.fsf@stark.xeocode.com>

* 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