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 7BBAA3A3ADB for ; Tue, 26 Oct 2004 10:53:24 +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 86970-04 for ; Tue, 26 Oct 2004 09:53:13 +0000 (GMT) Received: from cmailm4.svr.pol.co.uk (cmailm4.svr.pol.co.uk [195.92.193.211]) by svr1.postgresql.org (Postfix) with ESMTP id 9511D3A4350 for ; Tue, 26 Oct 2004 10:53:15 +0100 (BST) Received: from modem-757.monkey.dialup.pol.co.uk ([217.135.210.245] helo=[192.168.0.102]) by cmailm4.svr.pol.co.uk with esmtp (Exim 4.41) id 1CMO0u-0006Kz-JM; Tue, 26 Oct 2004 10:53:12 +0100 Subject: Re: [PATCHES] ARC Memory Usage analysis From: Simon Riggs To: Tom Lane Cc: Greg Stark , pgsql-hackers@postgresql.org 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 Organization: 2nd Quadrant Message-Id: <1098784258.6807.155.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Tue, 26 Oct 2004 10:50:58 +0100 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/881 X-Sequence-Number: 60384 On Tue, 2004-10-26 at 06: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. > ISTM that we should be optimizing the use of shared_buffers, not whats outside. Didn't you (Tom) already say that? BTW, very good ideas on how to proceed, but why bother? For me, if the sysadmin didn't give shared_buffers to PostgreSQL, its because the memory is intended for use by something else and so not available at all. At least not dependably. The argument against large shared_buffers because of swapping applies to that assumption also...the OS cache is too volatile to attempt to gauge sensibly. There's an argument for improving performance for people that haven't set their parameters correctly, but thats got to be a secondary consideration anyhow. -- Best Regards, Simon Riggs