From: Jan Wieck <JanWieck@Yahoo.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: Sat, 30 Oct 2004 09:40:39 -0400
Message-ID: <418399D7.6090204@Yahoo.com> (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 10/26/2004 1:53 AM, 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.
If we need another config option, it's not that we are running out of
possible names, is 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 #
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, tgl@sss.pgh.pa.us, gsstark@mit.edu, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
In-Reply-To: <418399D7.6090204@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