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 266CDDB2FF for ; Fri, 11 Nov 2005 15:28: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 03458-08 for ; Fri, 11 Nov 2005 19:28:52 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.eulerhermes.pl (host-ip43-68.crowley.pl [85.128.68.43]) by svr1.postgresql.org (Postfix) with ESMTP id 7FF6DDB170 for ; Fri, 11 Nov 2005 15:28:52 -0400 (AST) Received: from stunnel-ns1.warszawa-ext ([192.168.69.4] helo=[127.0.0.1] ident=nobody) by mail.eulerhermes.pl with esmtpa (Exim 4.42) id 1EaeZl-0008HP-8b; Fri, 11 Nov 2005 20:28:43 +0100 Message-ID: <4374F071.9010808@eulerhermes.pl> Date: Fri, 11 Nov 2005 20:26:41 +0100 From: Marcin Giedz User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: pl, en-us, en MIME-Version: 1.0 To: Tom Lane CC: "Jim C. Nasby" , pgsql-admin@postgresql.org Subject: Re: Xeon vs Opteron - second revision - tests and questions References: <200511091526.51685.marcin.giedz@eulerhermes.pl> <18347.1131563949@sss.pgh.pa.us> <4374E57F.5030201@eulerhermes.pl> <20815.1131736317@sss.pgh.pa.us> In-Reply-To: <20815.1131736317@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.019 required=5 tests=[AWL=0.019] X-Spam-Score: 0.019 X-Spam-Level: X-Archive-Number: 200511/140 X-Sequence-Number: 19513 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? Regards, Marcin >Usually people put them as far apart as they can stand (the constraint >on this is mainly how long you'd like to wait for recovery after a >system crash, and how much disk space you can spare for WAL logs). >Increasing the bg_writer parameters can be expected to dampen the spikes >but not eliminate them completely. > > regards, tom lane > > >