Re: Add GUC to tune glibc's malloc implementation.

From: Andres Freund <andres(at)anarazel(dot)de>
To: Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
Cc: pgsql-hackers(at)postgresql(dot)org, tomas(dot)vondra(at)enterprisedb(dot)com
Subject: Re: Add GUC to tune glibc's malloc implementation.
Date: 2023-06-26 20:59:07
Message-ID: 20230626205907.rmuzjwsbkzz7vdtw@awork3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2023-06-22 15:35:12 +0200, Ronan Dunklau wrote:
> This can cause problems. Let's take for example a table with 10k rows, and 32
> columns (as defined by a bench script David Rowley shared last year when
> discussing the GenerationContext for tuplesort), and execute the following
> query, with 32MB of work_mem:
>
> select * from t order by a offset 100000;
>
> I attached the results of the 10k rows / 32 columns / 32MB work_mem benchmark
> with different values for glibc_malloc_max_trim_threshold.

Could you provide instructions for the benchmark that don't require digging
into the archive to find an email by David?

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2023-06-26 21:03:48 Re: Add GUC to tune glibc's malloc implementation.
Previous Message Joel Jacobson 2023-06-26 20:55:03 Re: Do we want a hashset type?