X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8F77032A887 for ; Mon, 18 Oct 2004 20:37:58 +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 99517-03 for ; Mon, 18 Oct 2004 19:37:55 +0000 (GMT) Received: from smtp111.mail.sc5.yahoo.com (smtp111.mail.sc5.yahoo.com [66.163.170.9]) by svr1.postgresql.org (Postfix) with SMTP id 8065F32A34A for ; Mon, 18 Oct 2004 20:37:55 +0100 (BST) Received: from unknown (HELO jupiter.black-lion.info) (janwieck@68.80.245.191 with login) by smtp111.mail.sc5.yahoo.com with SMTP; 18 Oct 2004 19:37:54 -0000 Received: from [172.21.8.18] (ismtp.afilias.com [216.217.55.254]) (authenticated bits=0) by jupiter.black-lion.info (8.12.10/8.12.9) with ESMTP id i9IJbo94029432; Mon, 18 Oct 2004 15:37:52 -0400 (EDT) (envelope-from JanWieck@Yahoo.com) Message-ID: <41741B87.4090104@Yahoo.com> Date: Mon, 18 Oct 2004 15:37:43 -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: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some References: <200410081443.16109.josh@agliodbs.com> In-Reply-To: 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/264 X-Sequence-Number: 8740 On 10/14/2004 8:10 PM, Christopher Browne wrote: > Quoth simon@2ndquadrant.com ("Simon Riggs"): >> I say this: ARC in 8.0 PostgreSQL allows us to sensibly allocate as >> large a shared_buffers cache as is required by the database >> workload, and this should not be constrained to a small percentage >> of server RAM. > > I don't think that this particularly follows from "what ARC does." The combination of ARC together with the background writer is supposed to allow us to allocate the optimum even if that is large. The former implementation of the LRU without background writer would just hang the server for a long time during a checkpoint, which is absolutely inacceptable for any OLTP system. Jan > > "What ARC does" is to prevent certain conspicuous patterns of > sequential accesses from essentially trashing the contents of the > cache. > > If a particular benchmark does not include conspicuous vacuums or > sequential scans on large tables, then there is little reason to > expect ARC to have a noticeable impact on performance. > > It _could_ be that this implies that ARC allows you to get some use > out of a larger shared cache, as it won't get blown away by vacuums > and Seq Scans. But it is _not_ obvious that this is a necessary > truth. > > _Other_ truths we know about are: > > a) If you increase the shared cache, that means more data that is > represented in both the shared cache and the OS buffer cache, > which seems rather a waste; > > b) The larger the shared cache, the more pages there are for the > backend to rummage through before it looks to the filesystem, > and therefore the more expensive cache misses get. Cache hits > get more expensive, too. Searching through memory is not > costless. -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #