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 8CB44EAE486; Fri, 22 Oct 2004 23:03:00 +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 81138-05; Fri, 22 Oct 2004 22:03:05 +0000 (GMT) Received: from cmailg4.svr.pol.co.uk (cmailg4.svr.pol.co.uk [195.92.195.174]) by svr1.postgresql.org (Postfix) with ESMTP id B5A44EAE483; Fri, 22 Oct 2004 23:02:56 +0100 (BST) Received: from modem-3564.lion.dialup.pol.co.uk ([217.135.173.236] helo=[192.168.0.102]) by cmailg4.svr.pol.co.uk with esmtp (Exim 4.41) id 1CL7VD-0007Us-LU; Fri, 22 Oct 2004 23:03:15 +0100 Subject: Re: [PATCHES] ARC Memory Usage analysis From: Simon Riggs To: Tom Lane Cc: Jan Wieck , pgsql-patches@postgresql.org, pgsql-hackers@postgresql.org, josh@agliodbs.com In-Reply-To: <18764.1098477951@sss.pgh.pa.us> References: <1098471059.20926.49.camel@localhost.localdomain> <41796115.2020501@Yahoo.com> <18764.1098477951@sss.pgh.pa.us> Content-Type: text/plain Organization: 2nd Quadrant Message-Id: <1098482465.20926.122.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 22 Oct 2004 23:01:05 +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/768 X-Sequence-Number: 60271 On Fri, 2004-10-22 at 21:45, Tom Lane wrote: > Jan Wieck writes: > > What do you think about my other theory to make C actually 2x effective > > cache size and NOT to keep T1 in shared buffers but to assume T1 lives > > in the OS buffer cache? > > What will you do when initially fetching a page? It's not supposed to > go directly into T2 on first use, but we're going to have some > difficulty accessing a page that's not in shared buffers. I don't think > you can equate the T1/T2 dichotomy to "is in shared buffers or not". > Yes, there are issues there. I want Jan to follow his thoughts through. This is important enough that its worth it - there's only a few even attempting this. > You could maybe have a T3 list of "pages that aren't in shared buffers > anymore but we think are still in OS buffer cache", but what would be > the point? It'd be a sufficiently bad model of reality as to be pretty > much useless for stats gathering, I'd think. > The OS cache is in many ways a wild horse, I agree. Jan is trying to think of ways to harness it, whereas I had mostly ignored it - but its there. Raw disk usage never allowed this opportunity. For high performance systems, we can assume that the OS cache is ours to play with - what will we do with it? We need to use it for some purposes, yet would like to ignore it for others. -- Best Regards, Simon Riggs