Horton

RE: speeding up planning with partitions

Imai, Yoshikazu <imai.yoshikazu@jp.fujitsu.com>

View thread View on postgr.es
From: "Imai, Yoshikazu" <imai.yoshikazu@jp.fujitsu.com>
To: 'Amit Langote' <Langote_Amit_f8@lab.ntt.co.jp>, 'Amit Langote' <amitlangote09@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <david.rowley@2ndquadrant.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Jesper Pedersen <jesper.pedersen@redhat.com>
Date: 2019-03-20T09:40:34Z
Lists: pgsql-hackers 
Amit-san,

On Wed, Mar 20, 2019 at 9:07 AM, Amit Langote wrote:
> On 2019/03/20 17:36, Imai, Yoshikazu wrote:
> > On Wed, Mar 20, 2019 at 8:21 AM, Amit Langote wrote:
> >> On 2019/03/20 12:15, Imai, Yoshikazu wrote:
> >>> [select1024.sql]
> >>> \set a random (1, 1024)
> >>> select * from rt where a = :a;
> >>>
> >>> [pgbench]
> >>> pgbench -n -f select1024.sql -T 60
> >>
> >> Thank you.
> >>
> >> Could you please try with running pgbench for a bit longer than 60
> seconds?
> >
> > I run pgbench for 180 seconds but there are still difference.
> 
> Thank you very much.
> 
> > 1024: 7,004 TPS
> > 8192: 5,859 TPS
> >
> >
> > I also tested for another number of partitions by running pgbench for
> 60 seconds.
> >
> > num of part    TPS
> > -----------  -----
> > 128          7,579
> > 256          7,528
> > 512          7,512
> > 1024         7,257 (7274, 7246, 7252)
> > 2048         6,718 (6627, 6780, 6747)
> > 4096         6,472 (6434, 6565, 6416) (quoted from above (3)'s results)
> > 8192         6,008 (6018, 5999, 6007)
> >
> >
> > I checked whether there are the process which go through the number
> of partitions, but I couldn't find. I'm really wondering why this
> degradation happens.
> 
> Indeed, it's quite puzzling why.  Will look into this.

I don't know whether it is useful, but I noticed the usage of get_tabstat_entry increased when many partitions are scanned.

--
Yoshikazu Imai

Commits

  1. Clean up handling of constraint_exclusion and enable_partition_pruning.

  2. Add test case exercising formerly-unreached code in inheritance_planner.

  3. Speed up planning when partitions can be pruned at plan time.

  4. Avoid crash in partitionwise join planning under GEQO.

  5. Avoid passing query tlist around separately from root->processed_tlist.

  6. Build "other rels" of appendrel baserels in a separate step.

  7. Get rid of duplicate child RTE for a partitioned table.

  8. Rearrange make_partitionedrel_pruneinfo to avoid work when we can't prune.

  9. Don't copy PartitionBoundInfo in set_relation_partition_info.

  10. Move building of child base quals out into a new function

  11. Reorganize planner code moved in b60c39759908

  12. Move inheritance expansion code into its own file

  13. Fix inherited UPDATE/DELETE with UNION ALL subqueries.

  14. Rearrange planner to save the whole PlannerInfo (subroot) for a subquery.