Re: [PATCH] Use MAP_HUGETLB where supported (v3) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] Use MAP_HUGETLB where supported (v3)
Date
Msg-id 4022.1383145864@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Use MAP_HUGETLB where supported (v3)  (Sergey Konoplev <gray.ru@gmail.com>)
Responses Re: [PATCH] Use MAP_HUGETLB where supported (v3)  (Sergey Konoplev <gray.ru@gmail.com>)
List pgsql-hackers
Sergey Konoplev <gray.ru@gmail.com> writes:
> On Tue, Oct 29, 2013 at 9:31 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Say what?  There's never been any hugepages support in Postgres.

> There were an ability to back shared memory with hugepages when using
> <=9.2. I use it on ~30 servers for several years and it brings 8-17%
> of performance depending on the memory size. Here you will find
> several paragraphs of the description about how to do it
> https://github.com/grayhemp/pgcookbook/blob/master/database_server_configuration.md.

What this describes is how to modify Postgres to request huge pages.
That's hardly built-in support.

In any case, as David already explained, we don't do feature additions
in minor releases.  We'd be especially unlikely to make an exception
for this, since it has uncertain portability and benefits.  Anything
that carries portability risks has got to go through a beta testing
cycle before we'll unleash it on the masses.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Use MAP_HUGETLB where supported (v3)
Next
From: Merlin Moncure
Date:
Subject: Re: Fast insertion indexes: why no developments