Re: Any better plan for this query?.. - Mailing list pgsql-performance

From Dimitri
Subject Re: Any better plan for this query?..
Date
Msg-id 5482c80a0905110922tf958431ofe468e9c0fd9ac90@mail.gmail.com
Whole thread Raw
In response to Re: Any better plan for this query?..  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
Hi Tom,

it was not willing :-)
it just stayed so after various probes with a query plan.

Anyway, on 8.4 the default target is 100, an just by move it to 5 I
reached on 16cores  10.500 TPS instead of 8.000 initially. And I think
you have a good reason to keep it equal to 100 by default, isn't it?
;-)

And what about scalability on 32cores?..
Any idea?

Rgds,
-Dimitri

On 5/11/09, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Dimitri <dimitrik.fr@gmail.com> writes:
>> Anyone may explain me why analyze target may have so huge negative
>> secondary effect?..
>
> If these are simple queries, maybe what you're looking at is the
> increase in planning time caused by having to process 10x as much
> statistical data.  Cranking statistics_target to the max just because
> you can is not necessarily a good strategy.
>
>             regards, tom lane
>

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: What is the most optimal config parameters to keep stable write TPS ?..
Next
From: Dimitri
Date:
Subject: Re: What is the most optimal config parameters to keep stable write TPS ?..