pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Christophe Pettus <xof@thebuild.com>
Cc: David Gauthier <dfgpostgres@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Best practices for data buffer cache setting/tuning (v15)
Date: Mon, 29 Jan 2024 22:56:56 -0500
Message-ID: <ZbhziEoDaYwcVdEn@momjian.us> (raw)
In-Reply-To: <8D24CE5D-16B2-4962-A741-7C5CAD54FAC5@thebuild.com>
References: <CAEs=6Dm0K5NGJ09RG_dM4ptvE5V=bXCYEttd91G7_t=ZWO9rxg@mail.gmail.com>
	<8D24CE5D-16B2-4962-A741-7C5CAD54FAC5@thebuild.com>

On Mon, Jan 29, 2024 at 01:46:30PM -0800, Christophe Pettus wrote:
>
>
> > On Jan 29, 2024, at 11:39, David Gauthier <dfgpostgres@gmail.com>
> > wrote:
> >
> > Is there a document which makes recommendations on sizing data
> > buffer cache, tuning options which evict old/unused data in mem, and
> > cache fragmentation avoidance for a v15.3 DB ?
>
> On any modern system, set shared_buffers to 25% of instance RAM, and
> get on with life.
>
> I realize that seems glib, but small variations in shared_buffers make
> almost no significant difference in performance.  There are unusual
> workloads (like very high insert rate with few queries) that require
> different settings, but for most typical ELTP or data warehouse
> workloads, that is sufficient.

This blog entry might explain why Postgres requires less tuning of
shared buffers than other database systems:

        https://momjian.us/main/blogs/pgblog/2018.html#December_7_2018

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.





view thread (4+ messages)

Message-ID: <ZbhziEoDaYwcVdEn@momjian.us>
Permalink:  ../ZbhziEoDaYwcVdEn@momjian.us/
Also on:    postgresql.org/message-id/ZbhziEoDaYwcVdEn@momjian.us

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: bruce@momjian.us, xof@thebuild.com, dfgpostgres@gmail.com
  Subject: Re: Best practices for data buffer cache setting/tuning (v15)
  In-Reply-To: <ZbhziEoDaYwcVdEn@momjian.us>
  References: <CAEs=6Dm0K5NGJ09RG_dM4ptvE5V=bXCYEttd91G7_t=ZWO9rxg@mail.gmail.com> <8D24CE5D-16B2-4962-A741-7C5CAD54FAC5@thebuild.com> <ZbhziEoDaYwcVdEn@momjian.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