From: Justin Pryzby <pryzby@telsasoft.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: Michael Lewis <mlewis@entrata.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Daulat Ram <Daulat.Ram@exponential.com>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Subject: Re: Shared_buffers
Date: Tue, 12 Mar 2019 15:11:02 -0500
Message-ID: <20190312201102.GI23597@telsasoft.com> (raw)
In-Reply-To: <5C88107F.7040902@sqlexec.com>
References: <BL0PR01MB51871A89E9255FFCD13CC3839B480@BL0PR01MB5187.prod.exchangelabs.com>
<56099ac31c7cc1a4e8a51963e2674e7fe592b86f.camel@cybertec.at>
<CAHOFxGqT24bb_G9Ej3jAwBDLizfK1dwb+rXo62mP4zjB6iDRpA@mail.gmail.com>
<5C88107F.7040902@sqlexec.com>
On Tue, Mar 12, 2019 at 04:03:11PM -0400, MichaelDBA wrote:
> Set shared_buffers more accurately by using pg_buffercache extension and the
> related queries during high load times.
I've tuned ~40 postgres instances, primarily using log_checkpoints and
pg_stat_bgwriter, with custom RRD graphs. pg_buffercache does provide some
valuable insights, and I know it's commonly suggested to check histogram of
usagecounts, but I've never had any idea how to apply that to tune
shared_buffers.
Could you elaborate on what procedure you suggest ?
Justin
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: pryzby@telsasoft.com, MichaelDBA@sqlexec.com, mlewis@entrata.com, laurenz.albe@cybertec.at, Daulat.Ram@exponential.com, pgsql-performance@lists.postgresql.org
Subject: Re: Shared_buffers
In-Reply-To: <20190312201102.GI23597@telsasoft.com>
* 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