From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Grant Masan <grant(dot)massan(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Problem with database performance, Debian 4gb ram ? |
Date: | 2009-11-03 17:23:33 |
Message-ID: | f67928030911030923i31663c7ew8d75b04874cb568d@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Tue, Nov 3, 2009 at 7:13 AM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Grant Masan <grant(dot)massan(at)gmail(dot)com> wrote:
>
>
>> cpu_tuple_cost = 0.0030
>> cpu_index_tuple_cost = 0.0010
>> cpu_operator_cost = 0.0005
>
> Why did you make these adjustments? I usually have to change the
> ratio between page and cpu costs toward the other direction.
Is that because the database is mostly cached in memory? If I take the
documented descriptions of the costs parameters at face value, I find
that cpu_tuple_cost should be even lower yet.
Cheer,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2009-11-03 17:54:14 | Re: Problem with database performance, Debian 4gb ram ? |
Previous Message | Sam Jas | 2009-11-03 17:21:10 | Re: Connection Problems! |
From | Date | Subject | |
---|---|---|---|
Next Message | David Kerr | 2009-11-03 17:47:29 | Optimizer + bind variables |
Previous Message | Kevin Grittner | 2009-11-03 17:03:43 | Re: Queryplan within FTS/GIN index -search. |