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 D20BA3A3BF4 for ; Wed, 27 Oct 2004 03:28:16 +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 41904-03 for ; Wed, 27 Oct 2004 02:28:11 +0000 (GMT) Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112]) by svr1.postgresql.org (Postfix) with SMTP id 498FD3A3BE5 for ; Wed, 27 Oct 2004 03:28:15 +0100 (BST) Received: (qmail 83001 invoked by uid 0); 27 Oct 2004 02:28:16 -0000 Received: from unknown (63.231.195.9) by mpls-qmqp-01.inet.qwest.net with QMQP; 27 Oct 2004 02:28:16 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-09.inet.qwest.net with SMTP; 27 Oct 2004 02:28:15 -0000 Date: Tue, 26 Oct 2004 20:30:34 -0600 Message-Id: <1098844234.31930.45.camel@localhost.localdomain> From: "Scott Marlowe" To: "Tom Lane" Cc: "Greg Stark" , pgsql-hackers@postgresql.org Subject: Re: [PATCHES] ARC Memory Usage analysis 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> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit 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/921 X-Sequence-Number: 60424 On Mon, 2004-10-25 at 23:53, 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. 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?