From: Josh Berkus <josh@agliodbs.com>
To: pgsql-hackers@postgresql.org
Cc: Thomas F.O'Connell <tfo@sitening.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: PgSQL - Performance <pgsql-performance@postgresql.org>
Subject: Re: [PERFORM] [PATCHES] ARC Memory Usage analysis
Date: Tue, 26 Oct 2004 17:39:59 -0700
Message-ID: <200410261739.59814.josh@agliodbs.com> (raw)
In-Reply-To: <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com>
References: <1098471059.20926.49.camel@localhost.localdomain>
<1098780555.6807.136.camel@localhost.localdomain>
<74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com>
Thomas,
> As a result, I was intending to inflate the value of
> effective_cache_size to closer to the amount of unused RAM on some of
> the machines I admin (once I've verified that they all have a unified
> buffer cache). Is that correct?
Currently, yes. Right now, e_c_s is used just to inform the planner and make
index vs. table scan and join order decisions.
The problem which Simon is bringing up is part of a discussion about doing
*more* with the information supplied by e_c_s. He points out that it's not
really related to the *real* probability of any particular table being
cached. At least, if I'm reading him right.
--
--Josh
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, pgsql-hackers@postgresql.org, tfo@sitening.com, simon@2ndquadrant.com
Subject: Re: [PERFORM] [PATCHES] ARC Memory Usage analysis
In-Reply-To: <200410261739.59814.josh@agliodbs.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