X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BB4E2D1E905 for ; Sun, 29 Feb 2004 00:52:24 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 76369-03 for ; Sat, 28 Feb 2004 20:52:24 -0400 (AST) Received: from tht.net (vista.tht.net [216.126.88.2]) by svr1.postgresql.org (Postfix) with ESMTP id C602AD1E8A8 for ; Sat, 28 Feb 2004 20:52:20 -0400 (AST) Received: from [134.22.70.82] (dyn-70-82.tor.dsl.tht.net [134.22.70.82]) by tht.net (Postfix) with ESMTP id 80E0776A74; Sat, 28 Feb 2004 19:52:27 -0500 (EST) Subject: Re: WAL Optimisation - configuration and usage From: Rod Taylor To: Rob Fielding Cc: Postgresql Performance In-Reply-To: <4040E08C.1040408@dsvr.net> References: <4040E08C.1040408@dsvr.net> Content-Type: text/plain Message-Id: <1078015971.24316.9.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sat, 28 Feb 2004 19:52:52 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/331 X-Sequence-Number: 5855 > random_page_cost = 0.5 Not likely. The lowest this value should ever be is 1, and thats if you're using something like a ram drive. If you're drives are doing a ton of extra random IO due to the above (rather than sequential reads) it would lower the throughput quite a bit. Try a value of 2 for a while.