| From: | Alicja Kucharczyk <zaledwie10minut(at)gmail(dot)com> |
|---|---|
| To: | Roland Müller <rolmur(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Setting huge_pages=off when HugePages are allocated in Linux? |
| Date: | 2026-01-29 14:57:47 |
| Message-ID: | CAM=sWa5auURVFGJZ-wL9NS5vpV2AdN=mJBo6G4ZjXuE+cCGFfw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alicja Kucharczyk | 2026-01-29 15:09:08 | Re: Setting huge_pages=off when HugePages are allocated in Linux? |
| Previous Message | Roland Müller | 2026-01-29 11:31:17 | Re: Setting huge_pages=off when HugePages are allocated in Linux? |