pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jan Wieck <JanWieck@Yahoo.com>
To: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: Andy Ballingall <andy_ballingall@bigfoot.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Working on huge RAM based datasets
Date: Sun, 11 Jul 2004 10:12:46 -0400
Message-ID: <40F14ADE.4080402@Yahoo.com> (raw)
In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB34101AEC2@Herge.rcsinc.local>
References: <6EE64EF3AB31D5448D0007DD34EEB34101AEC2@Herge.rcsinc.local>

On 7/9/2004 10:16 AM, Merlin Moncure wrote:

>> What is it about the buffer cache that makes it so unhappy being able
> to
>> hold everything? I don't want to be seen as a cache hit fascist, but
> isn't
>> it just better if the data is just *there*, available in the
> postmaster's
>> address space ready for each backend process to access it, rather than
>> expecting the Linux cache mechanism, optimised as it may be, to have
> to do
>> the caching?
> 
> The disk cache on most operating systems is optimized.  Plus, keeping
> shared buffers low gives you more room to bump up the sort memory, which
> will make your big queries run faster.

Plus, the situation will change dramatically with 7.5 where the disk 
cache will have less information than the PG shared buffers, which will 
become sequential scan resistant and will know that a block was pulled 
in on behalf of vacuum and not because the regular database access 
pattern required it.


Jan

-- 
#======================================================================#
# 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 (16+ messages)  latest in thread

Message-ID: <40F14ADE.4080402@Yahoo.com>
Permalink:  ../40F14ADE.4080402@Yahoo.com/
Also on:    postgresql.org/message-id/40F14ADE.4080402@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, merlin.moncure@rcsonline.com, andy_ballingall@bigfoot.com
  Subject: Re: Working on huge RAM based datasets
  In-Reply-To: <40F14ADE.4080402@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