X-Original-To: pgsql-performance@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id 4D8B4475B47 for ; Sun, 16 Mar 2003 21:08:24 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2H28RL21189 for pgsql-performance@postgresql.org; Mon, 17 Mar 2003 10:08:27 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h2H28C721094; Mon, 17 Mar 2003 10:08:14 +0800 (WST) Message-ID: <021301c2ec2a$10cfca70$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Aaron Krowne" , Cc: References: <20030316060125.GD19570@vt.edu> Subject: Re: postgresql meltdown on PlanetMath.org Date: Mon, 17 Mar 2003 10:08:10 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Archive-Number: 200303/110 X-Sequence-Number: 1408 > - Lastly, I tried reducing the shared memory max and limiting postgresql > to more conservative values, although still not to the out-of-box > values. Right now shared memory max on the system is 128mb, > postgres's shared buffers are at 64mb, sort_mem is at 16mb, and > effective cache size is at 10mb. I found that 5000 shared buffers was best performance on my system. However, your problems are probably due to maybe not running vacuum, analyze, reindex, etc. Your queries may not be effectively indexed - EXPLAIN ANALYZE them all. Chris