public inbox for [email protected]  
help / color / mirror / Atom feed
From: Tom Lane <[email protected]>
To: Andrew Dunstan <[email protected]>
Cc: David Rowley <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: scale parallel_tuple_cost by tuple width
Date: Wed, 01 Apr 2026 15:27:54 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<CAApHDvpOPs-Ywcze5=eyi4s5hO1NM9RA8No20Q=s+0L3LiorHw@mail.gmail.com>
	<[email protected]>
	<[email protected]>

I wrote:
> macOS/M4-Pro:

> Width    Parallel(ms)   Serial(ms)      Speedup  Gather rows
> -----    ------------   ----------      -------  -----------
> 8             299.464      769.130        2.57x       242549
> 16            310.361      787.629        2.54x       243643
> 32            344.541      839.589        2.44x       242419
> 64            413.330      967.512        2.34x       238771
> 128           519.794     1185.757        2.28x       241440
> 256          1479.766     1823.559        1.23x       238615
> 384          2022.882     2326.823        1.15x       240617
> 512          2423.938     2778.995        1.15x       244752
> 768          3511.425     3934.384        1.12x       235814
> 1024         9905.073    12214.577        1.23x     10000000

On closer review, it looks like I carelessly allowed this test
to run in parallel with a buildfarm run.  Here are numbers
with an idle machine:

Width    Parallel(ms)   Serial(ms)      Speedup  Gather rows
-----    ------------   ----------      -------  -----------
8             281.881      758.167        2.69x       242549
16            300.997      791.184        2.63x       243643
32            340.815      842.715        2.47x       242419
64            401.282      985.711        2.46x       238771
128           507.066     1183.727        2.33x       241440
256           718.008     1667.830        2.32x       238615
384          1774.601     2224.726        1.25x       240617
512          2439.593     2784.242        1.14x       244752
768          3254.088     3698.615        1.14x       235814
1024         8990.584    12176.341        1.35x     10000000

This is interesting because while the speedup ratio was
pretty insensitive to row width on the x86_64 box, that's
far from true on the Apple box.

			regards, tom lane





view thread (6+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: scale parallel_tuple_cost by tuple width
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox