public inbox for [email protected]  
help / color / mirror / Atom feed
From: Alicja Kucharczyk <[email protected]>
To: Roland Müller <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: Ron Johnson <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: Setting huge_pages=off when HugePages are allocated in Linux?
Date: Thu, 29 Jan 2026 15:57:47 +0100
Message-ID: <CAM=sWa5auURVFGJZ-wL9NS5vpV2AdN=mJBo6G4ZjXuE+cCGFfw@mail.gmail.com> (raw)
In-Reply-To: <CA+8p0G2TAVw7+h2s60cPe3K9=YWPWjm+sf4a_aJOb=kC-E6BDQ@mail.gmail.com>
References: <CANzqJaD0Nj2SvXrGCM-p_TUaeN84TzRteo7jxqSdARaZDiXABA@mail.gmail.com>
	<[email protected]>
	<CA+8p0G2TAVw7+h2s60cPe3K9=YWPWjm+sf4a_aJOb=kC-E6BDQ@mail.gmail.com>

> When does it make sense to use hugepages in Postgresql?
>
Usually when your shared memory footprint is very large, i.e. primarily
very large shared_buffers. In practice, huge pages tend to pay off on
dedicated, high-throughput systems where shared_buffers is really big
(often tens of GB, and very commonly you start caring around ~100GB+) and
you have high concurrency / tight latency goals.


> Is usage of hugepages only available in release 18?
>
No, huge pages support has been around since PostgreSQL 9.4. But starting
with PostgreSQL 15, it’s much easier to size/configure because PostgreSQL
can tell you the required count via the runtime-computed setting
shared_memory_size_in_huge_pages, before that you needed to calculate it on
your own.

regards,
A.Kucharczyk


reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Setting huge_pages=off when HugePages are allocated in Linux?
  In-Reply-To: <CAM=sWa5auURVFGJZ-wL9NS5vpV2AdN=mJBo6G4ZjXuE+cCGFfw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox