From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
---|---|
To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Add bump memory context type and use it for tuplesorts |
Date: | 2024-03-05 02:42:10 |
Message-ID: | CAApHDvr_hGT=kaP0YXbKSNZtbRX+6hUkieCWEn2BULwW1uTr_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
There've been a few changes to the memory allocators in the past week
and some of these changes also need to be applied to bump.c. So, I've
rebased the patches on top of today's master. See attached.
I also re-ran the performance tests to check the allocation
performance against the recently optimised aset, generation and slab
contexts. The attached graph shows the time it took in seconds to
allocate 1GB of memory performing a context reset after 1MB. The
function I ran the test on is in the attached
pg_allocate_memory_test.patch.txt file.
The query I ran was:
select chksz,mtype,pg_allocate_memory_test_reset(chksz,
1024*1024,1024*1024*1024, mtype) from (values(8),(16),(32),(64))
sizes(chksz),(values('aset'),('generation'),('slab'),('bump'))
cxt(mtype) order by mtype,chksz;
David
Attachment | Content-Type | Size |
---|---|---|
v4-0001-Introduce-a-bump-memory-allocator.patch | text/plain | 30.6 KB |
v4-0002-Use-bump-memory-context-for-tuplesorts.patch | text/plain | 10.9 KB |
pg_allocate_memory_test.patch.txt | text/plain | 8.4 KB |
image/png | 64.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Guo | 2024-03-05 02:44:11 | Re: Support "Right Semi Join" plan shapes |
Previous Message | Richard Guo | 2024-03-05 02:33:23 | Re: Support "Right Semi Join" plan shapes |