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 05A7932BA82 for ; Fri, 15 Oct 2004 02:19:23 +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 25035-05 for ; Fri, 15 Oct 2004 01:19:16 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id E259A32B3AB for ; Fri, 15 Oct 2004 02:19:19 +0100 (BST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i9F1JFJ9025861 for ; Fri, 15 Oct 2004 01:19:15 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i9F0o1pt018278 for pgsql-performance@postgresql.org; Fri, 15 Oct 2004 00:50:01 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: First set of OSDL Shared Mem scalability results, some wierdness ... Date: Thu, 14 Oct 2004 20:10:59 -0400 Organization: cbbrowne Computing Inc Lines: 37 Message-ID: References: <200410081443.16109.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:XQr6mfAZWXpVgi6qa+zMNUctOcE= To: pgsql-performance@postgresql.org 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/204 X-Sequence-Number: 8680 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." "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. -- (format nil "~S@~S" "cbbrowne" "acm.org") http://linuxfinances.info/info/linuxdistributions.html "The X-Files are too optimistic. The truth is *not* out there..." -- Anthony Ord