Horton

Re: Estimating HugePages Requirements?

Don Seiler <don@seiler.us>

View thread View on postgr.es
From: Don Seiler <don@seiler.us>
To: Vijaykumar Jain <vijaykumarjain.github@gmail.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>, pgsql-admin <pgsql-admin@postgresql.org>
Date: 2021-06-09T18:52:19Z
Lists: pgsql-hackers 
On Wed, Jun 9, 2021 at 1:45 PM Vijaykumar Jain <
vijaykumarjain.github@gmail.com> wrote:

> Please ignore, if you have read the blog below, if not, at the end of it
> there is a github repo which has mem specs for various tpcc benchmarks.
> Ofcourse, your workload expectations may vary from the test scenarios
> used, but just in case.
>
> Settling the Myth of Transparent HugePages for Databases - Percona
> Database Performance Blog
> <https://www.percona.com/blog/2019/03/06/settling-the-myth-of-transparent-hugepages-for-databases/>
>

That blog post is about transparent huge pages, which is different than
HugePages I'm looking at here. We already disable THP as a matter of course.

-- 
Don Seiler
www.seiler.us

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.