Re: benchmark results comparing versions 15.2 and 16
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Andres Freund <andres@anarazel.de>
Cc: Alexander Lakhin <exclusion@gmail.com>, Michael Paquier <michael.paquier@gmail.com>, MARK CALLAGHAN <mdcallag@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2023-05-16T05:42:39Z
Lists: pgsql-hackers
On Mon, May 15, 2023 at 05:54:53PM -0700, Andres Freund wrote: > Yes. numactl --physcpubind ... in my case. Linux has an optimization where it > does not need to send an IPI when the client and server are scheduled on the > same core. For single threaded ping-pong tasks like pgbench -c1, that can make > a huge difference, particularly on larger CPUs. So you get a lot better > performance when forcing things to be colocated. Yes, that's not bringing the numbers higher with the simple cases I reported previously, either. Anyway, even if I cannot see such a high difference, I don't see how to bring back the original numbers you are reporting without doing more inlining and tying COERCE_SQL_SYNTAX more tightly within the executor's portions for the FuncExprs, and there are the collation assumptions as well. Perhaps that's not the correct thing to do with SQLValueFunction remaining around, but nothing can be done for v16, so I am planning to just revert the change before beta1, and look at it again later, from scratch. -- Michael
Commits
-
Add back SQLValueFunction for SQL keywords
- d8c3106bb60e 16.0 landed
-
Add missing TAP test name
- 1ab763fc22ad 16.0 cited
-
Have the planner consider Incremental Sort for DISTINCT
- 3c6fc58209f2 16.0 cited