Horton

Re: Estimating HugePages Requirements?

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: "Bossart, Nathan" <bossartn@amazon.com>
Cc: Michael Paquier <michael@paquier.xyz>, Fujii Masao <masao.fujii@oss.nttdata.com>, Justin Pryzby <pryzby@telsasoft.com>, Andres Freund <andres@anarazel.de>, Magnus Hagander <magnus@hagander.net>, Mark Dilger <mark.dilger@enterprisedb.com>, Don Seiler <don@seiler.us>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-09-13T15:49:49Z
Lists: pgsql-hackers 
On Fri, Sep 10, 2021 at 7:43 PM Bossart, Nathan <bossartn@amazon.com> wrote:
> > 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.

Hmm, that to me sounds like maybe only part of shared memory uses huge
pages and maybe we're just giving you the number required for that
part. I realize that it doesn't work that way but I don't know if
everyone will.

-- 
Robert Haas
EDB: http://www.enterprisedb.com

Commits

  1. Silence extra logging when using "postgres -C" on runtime-computed GUCs

  2. doc: Improve postgres command for shared_memory_size_in_huge_pages

  3. Introduce GUC shared_memory_size_in_huge_pages

  4. Support "postgres -C" with runtime-computed GUCs

  5. Make shared_memory_size a preset option

  6. Introduce GUC shared_memory_size

  7. Move the shared memory size calculation to its own function

  8. Add new GUC, max_worker_processes, limiting number of bgworkers.