From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Hugh Ranalli <hugh@whtc.ca>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Perplexing, regular decline in performance
Date: Wed, 26 Jun 2019 15:18:14 -0400
Message-ID: <8279.1561576694@sss.pgh.pa.us> (raw)
In-Reply-To: <20190626190743.GA15026@alvherre.pgsql>
References: <20190626190743.GA15026@alvherre.pgsql>
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> On 2019-Jun-26, Hugh Ranalli wrote:
>> From my research in preparing for the upgrade, I understood transparent
>> huge pages were a good thing, and should be enabled. Is this not correct?
> It is not.
Yeah ... they would be a good thing perhaps if the quality of the kernel
implementation were better. But there are way too many nasty corner
cases, at least with the kernel versions people around here have
experimented with. You're best off to disable THP and instead manually
arrange for Postgres' shared memory to use huge pages. I forget where
to look for docs about doing that, but I think we have some.
regards, tom lane
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: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, hugh@whtc.ca, pryzby@telsasoft.com, pgsql-performance@lists.postgresql.org
Subject: Re: Perplexing, regular decline in performance
In-Reply-To: <8279.1561576694@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox