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

From David Rowley
Subject Re: PG15 beta1 sort performance regression due to Generation context change
Date
Msg-id CAApHDvrivwkM2R1nb9gdWr2YzM=D-OCMSYZOU7Gw_VykvwR76w@mail.gmail.com
Whole thread Raw
In response to Re: PG15 beta1 sort performance regression due to Generation context change  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
On Tue, 31 May 2022 at 09:37, David Rowley <dgrowleyml@gmail.com> wrote:
> Likely it would have been more relevant to have tested this against
> master with 40af10b57 reverted. I'm running those now.

My machine just finished running the tests on master with the
generation context in tuplesort.c commented out so that it always uses
the allocset context.

In the attached graph, anything below 100% means that using the
generation context performs better than without.

In the test, each query runs 5 times. If I sum the average run time of
each query, master takes 41 min 43.8 seconds and without the use of
generation context it takes 43 mins 31.3 secs. So it runs in 95.88%
with the generation context.

Looking at the graph, you can easily see the slower performance for
the 64-byte tuples with 64MB of work_mem.  That's the only regression
of note. Many other cases are much faster.

I'm wondering if we should just do nothing about this. Any thoughts?

David

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: pg15b1: FailedAssertion("val > base", File: "...src/include/utils/relptr.h", Line: 67, PID: 30485)
Next
From: Peter Smith
Date:
Subject: Re: Skipping schema changes in publication