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 915A13A3EBC for ; Sat, 30 Oct 2004 17:53:42 +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 21298-10 for ; Sat, 30 Oct 2004 16:53:40 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 4EAF83A3EAA for ; Sat, 30 Oct 2004 17:53:40 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9UGraPG005986; Sat, 30 Oct 2004 12:53:37 -0400 (EDT) To: Jan Wieck Cc: Greg Stark , pgsql-hackers@postgresql.org Subject: Re: [PATCHES] ARC Memory Usage analysis In-reply-to: <418399D7.6090204@Yahoo.com> 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> <418399D7.6090204@Yahoo.com> Comments: In-reply-to Jan Wieck message dated "Sat, 30 Oct 2004 09:40:39 -0400" Date: Sat, 30 Oct 2004 12:53:36 -0400 Message-ID: <5985.1099155216@sss.pgh.pa.us> From: Tom Lane 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/1002 X-Sequence-Number: 60505 Jan Wieck writes: > On 10/26/2004 1:53 AM, Tom Lane wrote: >> Greg Stark writes: > Tom Lane 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? No, the point is that the value is not very trustworthy at the moment. regards, tom lane