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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andres Freund <andres(at)anarazel(dot)de>, Ronan Dunklau <ronan(dot)dunklau(at)aiven(dot)io>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Subject: Re: Add GUC to tune glibc's malloc implementation.
Date: 2023-08-01 20:54:29
Message-ID: C1E62E81-BC8C-4549-998F-7E5C561EAAE3@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Jun 2023, at 00:31, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2023-06-28 07:26:03 +0200, Ronan Dunklau wrote:
>> I see it as a way to have *some* sort of control over the malloc
>> implementation we use, instead of tuning our allocations pattern on top of it
>> while treating it entirely as a black box. As for the tuning, I proposed
>> earlier to replace this parameter expressed in terms of size as a "profile"
>> (greedy / conservative) to make it easier to pick a sensible value.
>
> I don't think that makes it very usable - we'll still have idle connections
> use up a lot more memory than now in some cases, and not in others, even
> though it doesn't help. And it will be very heavily dependent on the OS and
> glibc version.

Based on the comments in this thread and that no update has been posted
addressing the objections I will mark this returned with feedback. Please feel
free to resubmit to a future CF.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2023-08-01 21:03:03 Re: bug: ANALYZE progress report with inheritance tables
Previous Message Daniel Gustafsson 2023-08-01 20:29:05 Re: explain analyze rows=%.0f