Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 867BE9F9357 for ; Tue, 12 Dec 2006 11:58:36 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 95813-01 for ; Tue, 12 Dec 2006 11:58:16 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from skunk.mtbrook.bozemanpass.com (skunk.mtbrook.bozemanpass.com [69.145.82.195]) by postgresql.org (Postfix) with ESMTP id 5EEA09F9398 for ; Tue, 12 Dec 2006 11:58:22 -0400 (AST) Received: from [69.145.82.249] (unknown [69.145.82.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skunk.mtbrook.bozemanpass.com (Postfix) with ESMTP id D898B55836E; Tue, 12 Dec 2006 07:58:19 -0800 (PST) Message-ID: <457ED19D.7050301@boreham.org> Date: Tue, 12 Dec 2006 08:58:21 -0700 From: David Boreham User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Staubo CC: Michael Stone , pgsql-performance@postgresql.org Subject: Re: New to PostgreSQL, performance considerations References: <8a0c7af10612110531sbb019ck259fb16d131fdb50@mail.gmail.com> <60psaq5t94.fsf@dba2.int.libertyrms.com> <20061211173105.GH16692@mathom.us> <20061211184726.GI16692@mathom.us> <457DA782.3060506@modgraph-usa.com> <8a0c7af10612111422x6bdcc0c2p7cbfeb5a7b0e0374@mail.gmail.com> <2FC0D8E7-F8ED-452F-BB13-FB665B516E7F@purefiction.net> <20061212123252.GR16692@mathom.us> <42B14BCF-B745-4F94-B5EA-97997744A4D5@purefiction.net> In-Reply-To: <42B14BCF-B745-4F94-B5EA-97997744A4D5@purefiction.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/297 X-Sequence-Number: 22353 Alexander Staubo wrote: > No, fsync=on. The tps values are similarly unstable with fsync=off, > though -- I'm seeing bursts of high tps values followed by low-tps > valleys, a kind of staccato flow indicative of a write caching being > filled up and flushed. Databases with checkpointing typically exhibit this cyclical throughput syndrome. (put another way : this is to be expected and you are correct that it indicates buffered data being flushed to disk periodically).