Re: cpu_tuple_cost - Mailing list pgsql-performance

From Gregory Stark
Subject Re: cpu_tuple_cost
Date
Msg-id 87psy1mq66.fsf@stark.xeocode.com
Whole thread Raw
In response to cpu_tuple_cost  (Daniel Schuchardt <daniel_schuchardt@web.de>)
Responses Re: cpu_tuple_cost
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: cpu_tuple_cost
Next
From: Josh Berkus
Date:
Subject: Re: cpu_tuple_cost