From: Ronan Dunklau <ronan.dunklau@aiven.io>
To: David Rowley <dgrowleyml@gmail.com>
To: pgsql-hackers@lists.postgresql.org, Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tomas Vondra <tv@fuzzy.cz>
Subject: Re: Use generation context to speed up tuplesorts
Date: Thu, 16 Dec 2021 17:03:39 +0100
Message-ID: <36444569.XM6RcZxFsP@aivenronan> (raw)
In-Reply-To: <2740198.88bMQJbFj6@aivenronan>
References: <CAApHDvoH4ASzsAOyHcxkuY01Qf++8JJ0paw+03dk+W25tQEcNQ@mail.gmail.com>
<567d1ea7-bfeb-bd97-1a7f-b13d2770258c@enterprisedb.com>
<2740198.88bMQJbFj6@aivenronan>
Le jeudi 16 décembre 2021, 11:56:15 CET Ronan Dunklau a écrit :
> I will follow up with a benchmark of the test sorting a table with a width
> varying from 1 to 32 columns.
>
So please find attached another benchmark for that case.
The 3 different patchsets tested are:
- master
- fixed (David's original patch)
- adjust (Thomas growing blocks patch)
So it looks like tuning malloc for this would be very benificial for any kind
of allocation, and by doing so we reduce the problems seen with the growing
blocks patch to next to nothing, while keeping the ability to not allocate too
much memory from the get go.
I would like to try to implement some dynamic glibc malloc tuning, if that is
something we don't reject on principle from the get go.
--
Ronan Dunklau
Attachments:
[application/vnd.oasis.opendocument.spreadsheet] bench_results.ods (63.1K, ../36444569.XM6RcZxFsP@aivenronan/2-bench_results.ods)
download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: ronan.dunklau@aiven.io, dgrowleyml@gmail.com, tomas.vondra@enterprisedb.com, andres@anarazel.de, tv@fuzzy.cz
Subject: Re: Use generation context to speed up tuplesorts
In-Reply-To: <36444569.XM6RcZxFsP@aivenronan>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox