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 25AF23A3E71 for ; Sat, 30 Oct 2004 14:39:54 +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 80880-07 for ; Sat, 30 Oct 2004 13:39:48 +0000 (GMT) Received: from smtp109.mail.sc5.yahoo.com (smtp109.mail.sc5.yahoo.com [66.163.170.7]) by svr1.postgresql.org (Postfix) with SMTP id 283043A3E9D for ; Sat, 30 Oct 2004 14:39:51 +0100 (BST) Received: from unknown (HELO jupiter.black-lion.info) (janwieck@68.80.245.191 with login) by smtp109.mail.sc5.yahoo.com with SMTP; 30 Oct 2004 13:39:51 -0000 Received: from [172.21.8.18] (gv90209.gv.psu.edu [146.186.90.209]) (authenticated bits=0) by jupiter.black-lion.info (8.12.10/8.12.9) with ESMTP id i9UDdn94057594; Sat, 30 Oct 2004 09:39:49 -0400 (EDT) (envelope-from JanWieck@Yahoo.com) Message-ID: <418399D7.6090204@Yahoo.com> Date: Sat, 30 Oct 2004 09:40:39 -0400 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Greg Stark , pgsql-hackers@postgresql.org Subject: Re: [PATCHES] ARC Memory Usage analysis 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> In-Reply-To: <4887.1098770035@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.6 tagged_above=0.0 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL X-Spam-Level: * X-Archive-Number: 200410/1001 X-Sequence-Number: 60504 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? Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #