X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7D12ADB73B for ; Mon, 14 Nov 2005 13:50:54 -0400 (AST) 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 92488-07 for ; Mon, 14 Nov 2005 17:50:52 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from flake.decibel.org (flake.decibel.org [67.100.216.10]) by svr1.postgresql.org (Postfix) with ESMTP id 8EE25DB72B for ; Mon, 14 Nov 2005 13:50:52 -0400 (AST) Received: by flake.decibel.org (Postfix, from userid 1001) id C8DF815255; Mon, 14 Nov 2005 11:50:51 -0600 (CST) Date: Mon, 14 Nov 2005 11:50:51 -0600 From: "Jim C. Nasby" To: Marcin Giedz Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Xeon vs Opteron - second revision - tests and questions Message-ID: <20051114175051.GE18570@pervasive.com> References: <200511091526.51685.marcin.giedz@eulerhermes.pl> <18347.1131563949@sss.pgh.pa.us> <4374E57F.5030201@eulerhermes.pl> <20815.1131736317@sss.pgh.pa.us> <4374F071.9010808@eulerhermes.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4374F071.9010808@eulerhermes.pl> X-Operating-System: FreeBSD 4.11-RELEASE-p10 i386 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.008 required=5 tests=[AWL=0.008] X-Spam-Score: 0.008 X-Spam-Level: X-Archive-Number: 200511/149 X-Sequence-Number: 19522 On Fri, Nov 11, 2005 at 08:26:41PM +0100, Marcin Giedz wrote: > Tom Lane napisa?(a): > > >Marcin Giedz writes: > > > > > >>However I still can see 'spikey' performance but not as much as before > >>changes. What can I do more to eliminate or smooth these spikes? > >> > >> > > > >The spikes are certainly caused by checkpoints. You can fool with the > >checkpoint timing via checkpoint_segments and checkpoint_timeout. > > > > > I didn't mention before but I changed checkpoint_segments to 300 but no > checkpoint_time. Disk space doesn't matter at all ... time to > recovery.... shouldn't be very long (I don't have much experiences with > this as I do online backup every day). Can anyone please tell me what > values of these two parametres are reasonable? What Tom was refering to about 'time to recovery' is recovering from an unexpected database shutdown by replaying the WAL. If you go 5 minutes between syncing WAL to the mainline storage, then a worst-case recovery will take ~5 minutes (well, it could probably take longer, but it should be a linear relationship). The longer you make checkpoint interval, the longer you'll have to wait for the database to come back. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461