Re: The science of optimization in practical terms?

From: Bernd Helmle <mailings(at)oopsware(dot)de>
To: jd(at)commandprompt(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: The science of optimization in practical terms?
Date: 2009-02-13 13:05:41
Message-ID: 21D3E80B28D62569C2E8DFF6@teje
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

--On Donnerstag, Februar 12, 2009 16:06:31 -0800 "Joshua D. Drake"
<jd(at)commandprompt(dot)com> wrote:

> However, in recent times I have found that increasing cpu_tuple_cost,
> cpu_operator_cost and cpu_index_tuple_cost to be very useful. This is
> always in the scenario of, "queries were running fine for months and
> then all of a sudden, they are not". It is also always on systems that
> we are already maintaining and thus (in theory) are in good shape.

Hmm have you tried seq_page_cost and random_page_cost, too? I found them
really important especially if you have a steadily growing database or a
fully cached database to reflect the "real" disk access costs.

--
Thanks

Bernd

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zdenek Kotala 2009-02-13 13:11:16 Re: pg_upgrade project status
Previous Message Teodor Sigaev 2009-02-13 13:00:57 Re: GIN fast insert