Re: Estimating HugePages Requirements?

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Don Seiler <don@seiler.us>
Cc: Vijaykumar Jain <vijaykumarjain.github@gmail.com>, Julien Rouhaud <rjuju123@gmail.com>, pgsql-admin <pgsql-admin@postgresql.org>
Date: 2021-06-09T19:01:40Z
Lists: pgsql-hackers
On Wed, Jun  9, 2021 at 01:52:19PM -0500, Don Seiler wrote:
> 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
> 
> 
> 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.

This blog post talks about sizing huge pages too:

	https://momjian.us/main/blogs/pgblog/2021.html#April_12_2021

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  If only the physical world exists, free will is an illusion.




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.