pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sam R. <samruohola@yahoo.com>
To: david.rowley@2ndquadrant.com <david.rowley@2ndquadrant.com>
Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Cc: Jeff Janes <jeff.janes@gmail.com>
Subject: Re: To keep indexes in memory, is large enough effective_cache_size enough?
Date: Fri, 28 Sep 2018 04:45:25 +0000 (UTC)
Message-ID: <740776989.746571.1538109925380@mail.yahoo.com> (raw)
In-Reply-To: <CAKJS1f9W+nhzj_CV2wP++XH8j-onnv8boBqzqvu1vpe=uH2pQA@mail.gmail.com>
References: <1321418371.5650982.1537346138600.ref@mail.yahoo.com>
	<1321418371.5650982.1537346138600@mail.yahoo.com>
	<954477769.6489282.1537348503194@mail.yahoo.com>
	<CAMkU=1zSpXBPOeZDXoiFOtFHid+cmmAKLpV1Mh2mH=1TurPA3w@mail.gmail.com>
	<2104059362.5470282.1537368339686@mail.yahoo.com>
	<1685615979.2029662.1537857378862@mail.yahoo.com>
	<CAKJS1f9W+nhzj_CV2wP++XH8j-onnv8boBqzqvu1vpe=uH2pQA@mail.gmail.com>

Hi!
> The double buffering> itself does not slow anything down. 

That was what I was suspecting a little. Double buffering may not matter in our case, because the whole server is meant for PostgreSQL only.
In our case, we can e.g. reserve almost "all memory" for PostgreSQL (shared buffers etc.).

Please correct me if I am wrong.
BR Sam


 
 
  On ti, syysk. 25, 2018 at 23:55, David Rowley<david.rowley@2ndquadrant.com> wrote:   On Tue, 25 Sep 2018 at 18:36, Sam R. <samruohola@yahoo.com> wrote:
> Regarding double buffering: I do not know how much double buffering would slow down operations.
> It could also be possible to turn off kernel page cache on our DB server, to avoid double buffering. Although, we may still keep it in use.

I think you've misunderstood double buffering.  The double buffering
itself does not slow anything down. If the buffer is in shared buffers
already then it does not need to look any further for it. Double
buffering only becomes an issue when buffers existing 2 times in
memory causes other useful buffers to appear 0 times.

-- 
 David Rowley                  http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services
  

view thread (17+ messages)  latest in thread

Message-ID: <740776989.746571.1538109925380@mail.yahoo.com>
Permalink:  ../740776989.746571.1538109925380@mail.yahoo.com/
Also on:    postgresql.org/message-id/740776989.746571.1538109925380@mail.yahoo.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: samruohola@yahoo.com, david.rowley@2ndquadrant.com, pgsql-performance@lists.postgresql.org, jeff.janes@gmail.com
  Subject: Re: To keep indexes in memory, is large enough effective_cache_size enough?
  In-Reply-To: <740776989.746571.1538109925380@mail.yahoo.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