Re: Streaming read-ready sequential scan code - Mailing list pgsql-hackers

From Alexander Lakhin
Subject Re: Streaming read-ready sequential scan code
Date
Msg-id 63a63690-dd92-c809-0b47-af05459e95d1@gmail.com
Whole thread Raw
In response to Re: Streaming read-ready sequential scan code  (Andres Freund <andres@anarazel.de>)
Responses Re: Streaming read-ready sequential scan code
List pgsql-hackers
Hello,

I decided to compare v17 vs v16 performance (as I did the last year [1])
and discovered that v17 loses to v16 in the pg_tpcds (s64da_tpcds)
benchmark, query15 (and several others, but I focused on this one):
Best pg-src-master--.* worse than pg-src-16--.* by 52.2 percents (229.84 > 151.03): pg_tpcds.query15
Average pg-src-master--.* worse than pg-src-16--.* by 53.4 percents (234.20 > 152.64): pg_tpcds.query15
Please look at the full html report attached in case you're interested.

(I used my pg-mark tool to measure/analyze performance, but I believe the
same results can be seen without it.)

`git bisect` for this performance degradation pointed at b7b0f3f27...

[1] https://www.postgresql.org/message-id/b32bed1b-0746-9b20-1472-4bdc9ca66d52%40gmail.com

Best regards,
Alexander
Attachment

pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose
Next
From: Peter Eisentraut
Date:
Subject: Re: commitfest.postgresql.org is no longer fit for purpose