pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Christopher Browne <cbbrowne@acm.org>
Cc: pgsql-performance@postgresql.org
Subject: Re: First set of OSDL Shared Mem scalability results, some
Date: Mon, 18 Oct 2004 15:37:43 -0400
Message-ID: <41741B87.4090104@Yahoo.com> (raw)
In-Reply-To: <m33c0glu24.fsf@knuth.knuth.cbbrowne.com>
References: <200410081443.16109.josh@agliodbs.com>
	<NOEFLCFHBPDAFHEIPGBOEEDKCGAA.simon@2ndquadrant.com>
	<m33c0glu24.fsf@knuth.knuth.cbbrowne.com>

On 10/14/2004 8:10 PM, Christopher Browne wrote:

> Quoth simon@2ndquadrant.com ("Simon Riggs"):
>> I say this: ARC in 8.0 PostgreSQL allows us to sensibly allocate as
>> large a shared_buffers cache as is required by the database
>> workload, and this should not be constrained to a small percentage
>> of server RAM.
> 
> I don't think that this particularly follows from "what ARC does."

The combination of ARC together with the background writer is supposed 
to allow us to allocate the optimum even if that is large. The former 
implementation of the LRU without background writer would just hang the 
server for a long time during a checkpoint, which is absolutely 
inacceptable for any OLTP system.


Jan

> 
> "What ARC does" is to prevent certain conspicuous patterns of
> sequential accesses from essentially trashing the contents of the
> cache.
> 
> If a particular benchmark does not include conspicuous vacuums or
> sequential scans on large tables, then there is little reason to
> expect ARC to have a noticeable impact on performance.
> 
> It _could_ be that this implies that ARC allows you to get some use
> out of a larger shared cache, as it won't get blown away by vacuums
> and Seq Scans.  But it is _not_ obvious that this is a necessary
> truth.
> 
> _Other_ truths we know about are:
> 
>  a) If you increase the shared cache, that means more data that is
>     represented in both the shared cache and the OS buffer cache,
>     which seems rather a waste;
> 
>  b) The larger the shared cache, the more pages there are for the
>     backend to rummage through before it looks to the filesystem,
>     and therefore the more expensive cache misses get.  Cache hits
>     get more expensive, too.  Searching through memory is not
>     costless.


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #



view thread (41+ messages)  latest in thread

Message-ID: <41741B87.4090104@Yahoo.com>
Permalink:  ../41741B87.4090104@Yahoo.com/
Also on:    postgresql.org/message-id/41741B87.4090104@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: JanWieck@Yahoo.com, cbbrowne@acm.org
  Subject: Re: First set of OSDL Shared Mem scalability results, some
  In-Reply-To: <41741B87.4090104@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