[doc fix] Correct calculation of vm.nr_hugepages

From: "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: [doc fix] Correct calculation of vm.nr_hugepages
Date: 2018-02-19 07:05:47
Message-ID: 0A3221C70F24FB45833433255569204D1F8CC9B6@G01JPEXMBYT05
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


The current PostgreSQL documentation overestimates the number of huge pages (vm.nr_hugepages) because the calculation uses the maximum virtual address space. In practice, huge pages are only used for the anonymous shared memory segment. The attached patch fixes the documentation.

FYI, Oracle presents a shell script to calculate the number of huge pages for its shared memory segments:


Takayuki Tsunakawa

Attachment Content-Type Size
hugepage_size_doc.patch application/octet-stream 1023 bytes


Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2018-02-19 07:40:04 Re: spelling of enable_partition_wise_join
Previous Message Anthony Bykov 2018-02-19 06:37:40 Re: [PATCH] Add missing type conversion functions for PL/Python