pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Kenneth Marshall <ktm@is.rice.edu>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: pgsql-patches@postgresql.org
Cc: pgsql-hackers@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: [PATCHES] ARC Memory Usage analysis
Date: Mon, 25 Oct 2004 12:03:12 -0400
Message-ID: <20651.1098720192@sss.pgh.pa.us> (raw)
In-Reply-To: <417D1D01.3090401@Yahoo.com>
References: <1098471059.20926.49.camel@localhost.localdomain>
	<41796115.2020501@Yahoo.com>
	<20041022200955.GC4382@it.is.rice.edu>
	<417D1D01.3090401@Yahoo.com>

Jan Wieck <JanWieck@Yahoo.com> writes:
> This all only holds water, if the OS is allowed to swap out shared 
> memory. And that was my initial question, how likely is it to find this 
> to be true these days?

I think it's more likely that not that the OS will consider shared
memory to be potentially swappable.  On some platforms there is a shmctl
call you can make to lock your shmem in memory, but (a) we don't use it
and (b) it may well require privileges we haven't got anyway.

This has always been one of the arguments against making shared_buffers
really large, of course --- if the buffers aren't all heavily used, and
the OS decides to swap them to disk, you are worse off than you would
have been with a smaller shared_buffers setting.


However, I'm still really nervous about the idea of using
effective_cache_size to control the ARC algorithm.  That number is
usually entirely bogus.  Right now it is only a second-order influence
on certain planner estimates, and I am afraid to rely on it any more
heavily than that.

			regards, tom lane



view thread (32+ messages)  latest in thread

Message-ID: <20651.1098720192@sss.pgh.pa.us>
Permalink:  ../20651.1098720192@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20651.1098720192@sss.pgh.pa.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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, JanWieck@Yahoo.com, ktm@is.rice.edu, simon@2ndquadrant.com, pgsql-patches@postgresql.org, pgsql-hackers@postgresql.org, josh@agliodbs.com
  Subject: Re: [PATCHES] ARC Memory Usage analysis
  In-Reply-To: <20651.1098720192@sss.pgh.pa.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