Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E90B2650090 for ; Wed, 30 Jul 2008 14:52:38 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 51564-01-9 for ; Wed, 30 Jul 2008 14:52:32 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sd-2317.dedibox.fr (sd-2317.dedibox.fr [88.191.17.192]) by postgresql.org (Postfix) with ESMTP id DC2F46504F4 for ; Wed, 30 Jul 2008 14:51:53 -0300 (ADT) Received: from [192.168.10.64] (ASte-Genev-Bois-153-1-36-205.w83-200.abo.wanadoo.fr [83.200.26.205]) by sd-2317.dedibox.fr (Postfix) with ESMTP id DCAB92424; Wed, 30 Jul 2008 19:51:47 +0200 (CEST) Message-ID: <4890AA33.6000309@lelarge.info> Date: Wed, 30 Jul 2008 19:51:47 +0200 From: Guillaume Lelarge User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Dave North CC: pgsql-performance@postgresql.org Subject: Re: Database size Vs performance degradation References: <35FABCF85D99464FB00BC5123DC2A70A051D0FB8@s228130hz1ew09.apptix-01.savvis.net> <35FABCF85D99464FB00BC5123DC2A70A05244E0C@s228130hz1ew09.apptix-01.savvis.net> In-Reply-To: <35FABCF85D99464FB00BC5123DC2A70A05244E0C@s228130hz1ew09.apptix-01.savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.666 tagged_above=0 required=5 tests=SARE_SPEC_ROLEX_NOV5A=1.666 X-Spam-Level: * X-Archive-Number: 200807/255 X-Sequence-Number: 30855 Dave North a écrit : > [...] >> I'd suggest re-tuning as follows: >> >> 1) Increase shared_buffers to 10,000, test. Things should be >> a bit faster. >> >> 2) Increase checkpoint_segments to 30, test. What you want >> to watch for here whether there are periods where the server >> seems to freeze for a couple of seconds. That's a >> "checkpoint spike". If this happens, reduce >> checkpoint_segments to some sort of middle ground; some >> people never get above 10 before it's a problem. >> >> 3) Increase shared_buffers in larger chunks, as long as you >> don't see any problematic spikes you might usefully keep >> going until it's set to at least 100,000 before improvements >> level off. > > Do you happen to know if these are "reload" or "restart" tunable > parameters? I think I've read somewhere before that they are restart > parameters (assuming I've set SHMMAX high enough of course) > shared_buffers and checkpoint_segments both need a restart. > [...] > I have to say, I've learnt a whole load from you folks here this > morning...very enlightening. I'm now moving on to your site Greg! :) > There's much to learn from Greg's site. I was kinda impressed by all the good articles in it. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com