Re: PG15 beta1 sort performance regression due to Generation context change - Mailing list pgsql-hackers

From John Naylor
Subject Re: PG15 beta1 sort performance regression due to Generation context change
Date
Msg-id CAFBsxsG1Gv4q0vsfb9WTx2EfnhGiC=m32seLnWSMu7K+Jgz6fQ@mail.gmail.com
Whole thread Raw
In response to Re: PG15 beta1 sort performance regression due to Generation context change  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: PG15 beta1 sort performance regression due to Generation context change
List pgsql-hackers
I ran a shorter version of David's script with just 6-9 attributes to
try to reproduce the problem area (spreadsheet with graph attached).
My test is also different in that I compare HEAD with just reverting
40af10b57. This shows a 60% increase in HEAD in runtime for 64MB
workmem and 64 byte tuples. It also shows a 20% regression for 32MB
workmem and 64 byte tuples.

I don't have anything to add to the discussion about whether something
needs to be done here for PG15. If anything, changing work_mem is an
easy to understand (although sometimes not practical) workaround.
-- 
John Naylor
EDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Jakub Wartak
Date:
Subject: RE: effective_io_concurrency and NVMe devices
Next
From: "Thibaud W."
Date:
Subject: Proposal: adding a better description in psql command about large objects