pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: pgsql-patches@postgresql.org
Cc: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: [PATCHES] ARC Memory Usage analysis
Date: Fri, 22 Oct 2004 23:01:05 +0100
Message-ID: <1098482465.20926.122.camel@localhost.localdomain> (raw)
In-Reply-To: <18764.1098477951@sss.pgh.pa.us>
References: <1098471059.20926.49.camel@localhost.localdomain>
	<41796115.2020501@Yahoo.com>
	<18764.1098477951@sss.pgh.pa.us>

On Fri, 2004-10-22 at 21:45, Tom Lane wrote:
> Jan Wieck <JanWieck@Yahoo.com> writes:
> > What do you think about my other theory to make C actually 2x effective 
> > cache size and NOT to keep T1 in shared buffers but to assume T1 lives 
> > in the OS buffer cache?
> 
> What will you do when initially fetching a page?  It's not supposed to
> go directly into T2 on first use, but we're going to have some
> difficulty accessing a page that's not in shared buffers.  I don't think
> you can equate the T1/T2 dichotomy to "is in shared buffers or not".
> 

Yes, there are issues there. I want Jan to follow his thoughts through.
This is important enough that its worth it - there's only a few even
attempting this.

> You could maybe have a T3 list of "pages that aren't in shared buffers
> anymore but we think are still in OS buffer cache", but what would be
> the point?  It'd be a sufficiently bad model of reality as to be pretty
> much useless for stats gathering, I'd think.
> 

The OS cache is in many ways a wild horse, I agree. Jan is trying to
think of ways to harness it, whereas I had mostly ignored it - but its
there. Raw disk usage never allowed this opportunity.

For high performance systems, we can assume that the OS cache is ours to
play with - what will we do with it? We need to use it for some
purposes, yet would like to ignore it for others.

-- 
Best Regards, Simon Riggs




view thread (32+ messages)  latest in thread

Message-ID: <1098482465.20926.122.camel@localhost.localdomain>
Permalink:  ../1098482465.20926.122.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1098482465.20926.122.camel@localhost.localdomain

 · 

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: simon@2ndquadrant.com, tgl@sss.pgh.pa.us, JanWieck@Yahoo.com, pgsql-patches@postgresql.org, pgsql-hackers@postgresql.org, josh@agliodbs.com
  Subject: Re: [PATCHES] ARC Memory Usage analysis
  In-Reply-To: <1098482465.20926.122.camel@localhost.localdomain>

* 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