Thread: [GENERAL] Largepages in Windows
Does PostgreSQL 9.4 support large pages in windows? The setting is there in the postgresql.conf, but I cant tell if it is supported in windows?
--
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
'If at first you dont succeed, dont take up skydiving.'
On 01/17/2017 07:20 AM, Andrew Kerber wrote: > Does PostgreSQL 9.4 support large pages in windows? The setting is > there in the postgresql.conf, but I cant tell if it is supported in windows? Are you talking about this?: https://www.postgresql.org/docs/9.4/static/runtime-config-resource.html huge_pages (enum) Enables/disables the use of huge memory pages. Valid values are try (the default), on, and off. At present, this feature is supported only on Linux. The setting is ignored on other systems when set to try. The use of huge pages results in smaller page tables and less CPU time spent on memory management, increasing performance. For more details, see Section 17.4.4. With huge_pages set to try, the server will try to use huge pages, but fall back to using normal allocation if that fails. With on, failure to use huge pages will prevent the server from starting up. With off, huge pages will not be used. > > -- > Andrew W. Kerber > > 'If at first you dont succeed, dont take up skydiving.' -- Adrian Klaver adrian.klaver@aklaver.com
Thats what I needed, thank you. Windows generally calls them large pages, AIX also calls them large pages, really they are typically only called hugepages on Linux.
On Tue, Jan 17, 2017 at 9:28 AM, Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 01/17/2017 07:20 AM, Andrew Kerber wrote:Does PostgreSQL 9.4 support large pages in windows? The setting is
there in the postgresql.conf, but I cant tell if it is supported in windows?
Are you talking about this?:
https://www.postgresql.org/docs/9.4/static/runtime-config- resource.html
huge_pages (enum)
Enables/disables the use of huge memory pages. Valid values are try (the default), on, and off.
At present, this feature is supported only on Linux. The setting is ignored on other systems when set to try.
The use of huge pages results in smaller page tables and less CPU time spent on memory management, increasing performance. For more details, see Section 17.4.4.
With huge_pages set to try, the server will try to use huge pages, but fall back to using normal allocation if that fails. With on, failure to use huge pages will prevent the server from starting up. With off, huge pages will not be used.--
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
Adrian Klaver
adrian.klaver@aklaver.com
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
'If at first you dont succeed, dont take up skydiving.'
Andrew Kerber <andrew.kerber@gmail.com> writes: > Does PostgreSQL 9.4 support large pages in windows? The setting is there > in the postgresql.conf, but I cant tell if it is supported in windows? No, but there's a pending patch for that: https://www.postgresql.org/message-id/flat/0A3221C70F24FB45833433255569204D1F5F1751@G01JPEXMBYT05 Looks like it's blocked on the question of what privileges are required to use the feature. regards, tom lane
Oh, I can answer that. The owner of the postgreSQL executable must have the privilege to lock pages in memory.
On Tue, Jan 17, 2017 at 9:38 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Andrew Kerber <andrew.kerber@gmail.com> writes:
> Does PostgreSQL 9.4 support large pages in windows? The setting is there
> in the postgresql.conf, but I cant tell if it is supported in windows?
No, but there's a pending patch for that:
https://www.postgresql.org/message-id/flat/ 0A3221C70F24FB4583343325556920 4D1F5F1751@G01JPEXMBYT05
Looks like it's blocked on the question of what privileges are required
to use the feature.
regards, tom lane
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
'If at first you dont succeed, dont take up skydiving.'