Re: Estimating HugePages Requirements?

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, "Andres Freund" <andres(at)anarazel(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, "Mark Dilger" <mark(dot)dilger(at)enterprisedb(dot)com>, Don Seiler <don(at)seiler(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Estimating HugePages Requirements?
Date: 2021-09-10 23:43:40
Message-ID: 7E4B78B7-4B8C-41D1-862D-B0BDC3432F83@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On 9/10/21, 1:02 PM, "Robert Haas" <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 9, 2021 at 5:53 PM Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
>> I think it might be clearer to
>> somehow indicate that the value is essentially the size of the main
>> shared memory area in terms of the huge page size, but I'm not sure
>> how to do that concisely. Perhaps it is enough to just make sure the
>> description of "huge_pages_required" is detailed enough.
>
> shared_memory_size_in_huge_pages? It's kinda long, but a long name
> that you can understand without reading the docs is better than a
> short one where you can't.

I think that's an improvement. The only other idea I have at the
moment is num_huge_pages_required_for_shared_memory.

Nathan

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Gokan Atmaca 2021-09-11 15:41:28 Re: PgBackRest PITR restore
Previous Message Robert Haas 2021-09-10 20:01:23 Re: Estimating HugePages Requirements?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2021-09-11 01:50:17 Re: SQL:2011 application time
Previous Message Melanie Plageman 2021-09-10 22:16:28 Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?)