Re: WIP: Upper planner pathification - Mailing list pgsql-hackers

From Teodor Sigaev
Subject Re: WIP: Upper planner pathification
Date
Msg-id 56D5B09C.5010405@sigaev.ru
Whole thread Raw
In response to Re: WIP: Upper planner pathification  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP: Upper planner pathification  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: WIP: Upper planner pathification  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> I do not think the patch will make a lot of performance difference as-is;
> its value is more in what it will let us do later.  There are a couple of
Yep, for now on my notebook (best from 5 tries):
% pgbench -i -s 3000
% pgbench  -s 3000 -c 4 -j 4 -P 1 -T 60
HEAD    569 tps
patched 542 tps
% pgbench  -s 3000 -c 4 -j 4 -P 1 -T 60 -S
HEAD    9500 tps
patched 9458 tps

Looks close to measurement error, but may be explained increased amount of work 
for planning. Including, may be, more complicated path tree.

> this kind of optimization to chance.  But the patch is big enough already,
> so that (and a lot of other things) are getting left for later.
Agree

-- 
Teodor Sigaev                                   E-mail: teodor@sigaev.ru
  WWW: http://www.sigaev.ru/
 



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: PoC: Partial sort
Next
From: Alvaro Herrera
Date:
Subject: Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.