From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Stark <gsstark@mit.edu>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
Date: Tue, 26 Oct 2004 10:50:58 +0100
Message-ID: <1098784258.6807.155.camel@localhost.localdomain> (raw)
In-Reply-To: <4887.1098770035@sss.pgh.pa.us>
References: <1098471059.20926.49.camel@localhost.localdomain>
<41796115.2020501@Yahoo.com>
<20041022200955.GC4382@it.is.rice.edu>
<417D1D01.3090401@Yahoo.com>
<20651.1098720192@sss.pgh.pa.us>
<87mzyavhxc.fsf@stark.xeocode.com>
<87hdoiv62b.fsf@stark.xeocode.com>
<790.1098741205@sss.pgh.pa.us>
<878y9uukgb.fsf@stark.xeocode.com>
<4887.1098770035@sss.pgh.pa.us>
On Tue, 2004-10-26 at 06:53, Tom Lane wrote:
> Greg Stark <gsstark@mit.edu> writes:
> > Tom Lane <tgl@sss.pgh.pa.us> writes:
> >> Another issue is what we do with the effective_cache_size value once we
> >> have a number we trust. We can't readily change the size of the ARC
> >> lists on the fly.
>
> > Huh? I thought effective_cache_size was just used as an factor the cost
> > estimation equation.
>
> Today, that is true. Jan is speculating about using it as a parameter
> of the ARC cache management algorithm ... and that worries me.
>
ISTM that we should be optimizing the use of shared_buffers, not whats
outside. Didn't you (Tom) already say that?
BTW, very good ideas on how to proceed, but why bother?
For me, if the sysadmin didn't give shared_buffers to PostgreSQL, its
because the memory is intended for use by something else and so not
available at all. At least not dependably. The argument against large
shared_buffers because of swapping applies to that assumption also...the
OS cache is too volatile to attempt to gauge sensibly.
There's an argument for improving performance for people that haven't
set their parameters correctly, but thats got to be a secondary
consideration anyhow.
--
Best Regards, Simon Riggs
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, gsstark@mit.edu, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
In-Reply-To: <1098784258.6807.155.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