From: Scott Marlowe <smarlowe@qwest.net>
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 20:30:34 -0600
Message-ID: <1098844234.31930.45.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 Mon, 2004-10-25 at 23: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.
Because it's so often set wrong I take it. But if it's set right, and
it makes the the database faster to pay attention to it, then I'd be in
favor of it. Or at least having a switch to turn on the ARC buffer's
ability to look at it.
Or is it some other issue, having to do with the idea of knowing
effective cache size cause a positive effect overall on the ARC
algorhythm?
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: smarlowe@qwest.net, tgl@sss.pgh.pa.us, gsstark@mit.edu, pgsql-hackers@postgresql.org
Subject: Re: [PATCHES] ARC Memory Usage analysis
In-Reply-To: <1098844234.31930.45.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