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 81E8A32C59B for ; Thu, 14 Oct 2004 05:17:51 +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 42297-04 for ; Thu, 14 Oct 2004 04:17:42 +0000 (GMT) Received: from smtp108.mail.sc5.yahoo.com (smtp108.mail.sc5.yahoo.com [66.163.170.6]) by svr1.postgresql.org (Postfix) with SMTP id D2F9E32A60E for ; Thu, 14 Oct 2004 05:17:41 +0100 (BST) Received: from unknown (HELO jupiter.black-lion.info) (janwieck@68.80.245.191 with login) by smtp108.mail.sc5.yahoo.com with SMTP; 14 Oct 2004 04:17:40 -0000 Received: from [172.21.8.18] ([192.168.192.101]) (authenticated bits=0) by jupiter.black-lion.info (8.12.10/8.12.9) with ESMTP id i9E4HX94074613; Thu, 14 Oct 2004 00:17:34 -0400 (EDT) (envelope-from JanWieck@Yahoo.com) Message-ID: <416DFDDE.5070600@Yahoo.com> Date: Thu, 14 Oct 2004 00:17:34 -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: Greg Stark Cc: Christopher Browne , pgsql-performance@postgresql.org Subject: Re: First set of OSDL Shared Mem scalability results, some References: <200410081443.16109.josh@agliodbs.com> <416DCCFF.70304@Yahoo.com> <871xg25538.fsf@stark.xeocode.com> In-Reply-To: <871xg25538.fsf@stark.xeocode.com> 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=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/189 X-Sequence-Number: 8665 On 10/13/2004 11:52 PM, Greg Stark wrote: > Jan Wieck writes: > >> On 10/8/2004 10:10 PM, Christopher Browne wrote: >> >> > josh@agliodbs.com (Josh Berkus) wrote: >> >> I've been trying to peg the "sweet spot" for shared memory using >> >> OSDL's equipment. With Jan's new ARC patch, I was expecting that >> >> the desired amount of shared_buffers to be greatly increased. This >> >> has not turned out to be the case. >> > That doesn't surprise me. >> >> Neither does it surprise me. > > There's been some speculation that having a large shared buffers be about 50% > of your RAM is pessimal as it guarantees the OS cache is merely doubling up on > all the buffers postgres is keeping. I wonder whether there's a second sweet > spot where the postgres cache is closer to the total amount of RAM. Which would require that shared memory is not allowed to be swapped out, and that is allowed in Linux by default IIRC, not to completely distort the entire test. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #