X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 0C370D1B443 for ; Thu, 4 Dec 2003 20:27:57 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 14628-06 for ; Thu, 4 Dec 2003 16:27:26 -0400 (AST) Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by svr1.postgresql.org (Postfix) with ESMTP id 29C31D1B476 for ; Thu, 4 Dec 2003 16:27:25 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-30.mail.demon.net with esmtp (Exim 3.35 #1) id 1AS04L-0002XU-0U; Thu, 04 Dec 2003 20:27:25 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 924F117336; Thu, 4 Dec 2003 20:27:24 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id CEEFF17331; Thu, 4 Dec 2003 20:27:22 +0000 (GMT) From: Richard Huxton To: Jack Coates , josh@agliodbs.com Subject: Re: tuning questions Date: Thu, 4 Dec 2003 20:27:22 +0000 User-Agent: KMail/1.5 Cc: pgsql-performance References: <1070553983.6498.52.camel@cletus.lyris.com> <200312041120.21124.josh@agliodbs.com> <1070567455.13923.83.camel@cletus.lyris.com> In-Reply-To: <1070567455.13923.83.camel@cletus.lyris.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200312042027.22223.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/96 X-Sequence-Number: 4956 On Thursday 04 December 2003 19:50, Jack Coates wrote: > > I'm trying to set Postgres's shared memory usage in a fashion that > allows it to return requested results quickly. Unfortunately, none of > these changes allow PG to use more than a little under 300M RAM. > vacuumdb --analyze is now taking an inordinate amount of time as well > (40 minutes and counting), so that change needs to be rolled back. You don't want PG to use all your RAM, it's designed to let the underlying OS do a lot of caching for it. Probably worth having a look at vmstat/iostat and see if it's saturating on I/O. -- Richard Huxton Archonet Ltd