Re: PG15 beta1 sort performance regression due to Generation context change

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG15 beta1 sort performance regression due to Generation context change
Date: 2022-05-25 12:35:27
Message-ID: CAApHDvoSkWyjnt7a5tcenP5vUhokbBJ46RugMvB4snkV5ZkmMw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 25 May 2022 at 15:09, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I didn't test the performance of an aset.c context. I imagine it's
> likely to be less overhead due to aset.c being generally slower from
> having to jump through a few more hoops during palloc/pfree.

I've attached the results from doing the same test with a standard
allocset context.

With the exception of the 8 byte chunk size test, there just seems to
be a 3-4% slowdown on my machine.

David

Attachment Content-Type Size
master_vs_memorycontextlink_for_aset.txt text/plain 336 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-05-25 12:44:23 Re: doc: CREATE FOREIGN TABLE .. PARTITION OF .. DEFAULT
Previous Message Robert Haas 2022-05-25 12:25:44 Re: HOLD_INTERRUPTS() vs ProcSignalBarrier