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 78D0132A585 for ; Mon, 18 Oct 2004 21:59:03 +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 27745-01 for ; Mon, 18 Oct 2004 20:58:53 +0000 (GMT) Received: from davinci.ethosmedia.com (server226.ethosmedia.com [209.128.84.226]) by svr1.postgresql.org (Postfix) with ESMTP id B4E8532A552 for ; Mon, 18 Oct 2004 21:58:51 +0100 (BST) Received: from [64.81.245.111] (account josh@agliodbs.com HELO temoku.sf.agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 6524976 for pgsql-performance@postgresql.org; Mon, 18 Oct 2004 14:00:15 -0700 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: pgsql-performance@postgresql.org Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... Date: Mon, 18 Oct 2004 14:00:45 -0700 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410181400.45005.josh@agliodbs.com> 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/267 X-Sequence-Number: 8743 Simon, > I agree that you could test this by running on a bigger or smaller server, > i.e. one with more or less RAM. Running on a faster/slower server at the > same time might alter the results and confuse the situation. Unfortunately, a faster server is the only option I have that also has more RAM. If I double the RAM and double the processors at the same time, what would you expect to happen to the shared_buffers curve? -- --Josh Josh Berkus Aglio Database Solutions San Francisco