X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9AB353A4521; Wed, 27 Oct 2004 01:37:51 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 05354-10; Wed, 27 Oct 2004 00:37:47 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id EA2653A4523; Wed, 27 Oct 2004 01:37:49 +0100 (BST) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6560124; Tue, 26 Oct 2004 17:39:16 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-hackers@postgresql.org Subject: Re: [PERFORM] [PATCHES] ARC Memory Usage analysis Date: Tue, 26 Oct 2004 17:39:59 -0700 User-Agent: KMail/1.6.2 Cc: Thomas F.O'Connell , Simon Riggs , PgSQL - Performance References: <1098471059.20926.49.camel@localhost.localdomain> <1098780555.6807.136.camel@localhost.localdomain> <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com> In-Reply-To: <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410261739.59814.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/917 X-Sequence-Number: 60420 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