X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C934D329EAD for ; Wed, 15 Sep 2004 19:37:07 +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 52269-03 for ; Wed, 15 Sep 2004 18:37:03 +0000 (GMT) Received: from gghcwest.com (adsl-64-164-133-219.dsl.snfc21.pacbell.net [64.164.133.219]) by svr1.postgresql.org (Postfix) with ESMTP id 2EBBD329EA9 for ; Wed, 15 Sep 2004 19:37:02 +0100 (BST) Received: from localhost.localdomain (toonses.gghcwest.com [192.168.168.115]) by gghcwest.com (8.12.10/8.12.9) with ESMTP id i8FIb0st005292 for ; Wed, 15 Sep 2004 11:37:01 -0700 Received: from jwb by localhost.localdomain with local (Exim 4.34) id 1C7ede-0002SU-Oi for pgsql-general@postgresql.org; Wed, 15 Sep 2004 11:36:18 -0700 Subject: Re: disk performance benchmarks From: "Jeffrey W. Baker" To: pgsql-general@postgresql.org In-Reply-To: References: <1095185498.5792.12.camel@localhost.localdomain> <003801c49b07$f33b6990$ad01a8c0@zaphod> <1095264696.8243.0.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1095273378.9384.0.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 15 Sep 2004 11:36:18 -0700 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: 200409/722 X-Sequence-Number: 65928 On Wed, 2004-09-15 at 10:53, Vivek Khera wrote: > >>>>> "JWB" == Jeffrey W Baker writes: > > JWB> All these replies are really interesting, but the point is not that my > JWB> RAIDs are too slow, or that my CPUs are too slow. My point is that, for > JWB> long stretches of time, by database doesn't come anywhere near using the > JWB> capacity of the hardware. And I think that's odd and would like to > JWB> config it to "false". > > Have you tried to increase your checkpoing_segments? I get the > suspicion that you're checkpointing every 3 minutes constantly. > You'll have to restart the postmaster for this setting to take effect, > I believe. I have checkpoint_segments set to 24, but I get the feeling that making it larger may have the opposite effect of what I want, by extending the period during which the DB makes no progress. -jwb