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 DF96AD1B269 for ; Mon, 12 Jul 2004 11:38:16 -0300 (ADT) 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 72806-03 for ; Mon, 12 Jul 2004 14:38:09 +0000 (GMT) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7FAEBD1B1AB for ; Mon, 12 Jul 2004 11:37:58 -0300 (ADT) Received: from [134.22.68.4] (dyn-68-4.tor.dsl.tht.net [134.22.68.4]) by tht.net (Postfix) with ESMTP id 0FBCA76AF9; Mon, 12 Jul 2004 10:38:11 -0400 (EDT) Subject: Re: Working on huge RAM based datasets From: Rod Taylor To: Christopher Browne Cc: Postgresql Performance In-Reply-To: References: <6EE64EF3AB31D5448D0007DD34EEB34101AEC2@Herge.rcsinc.local> <40F14ADE.4080402@Yahoo.com> Content-Type: text/plain Message-Id: <1089643087.42256.7.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 12 Jul 2004 10:38:08 -0400 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: 200407/63 X-Sequence-Number: 7454 > What would be most interesting to see is whether this makes it wise to > increase shared buffer size. It may be more effective to bump down > the cache a little, and bump up sort memory; hard to tell. How do we go about scheduling tests with the OSDL folks? If they could do 10 runs with buffers between 1k and 500k it would help us get a broad view of the situation.