X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id E3F6052913
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 15 Jul 2005 13:03:23 -0300 (ADT)
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 79139-08
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Fri, 15 Jul 2005 16:03:15 +0000 (GMT)
Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36])
	by svr1.postgresql.org (Postfix) with ESMTP id A6FC4528DD
	for <pgsql-performance@postgresql.org>;
	Fri, 15 Jul 2005 13:03:11 -0300 (ADT)
Received: from [127.0.0.1] (really [68.3.22.74]) by lakermmtao03.cox.net
	(InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP
	id <20050715160310.LTGV23050.lakermmtao03.cox.net@[127.0.0.1]>;
	Fri, 15 Jul 2005 12:03:10 -0400
Message-ID: <42D7DE40.3070507@works4me.com>
Date: Fri, 15 Jul 2005 09:03:12 -0700
From: Dennis <dennis@works4me.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: David Mitchell <david.mitchell@telogis.com>
Cc: Qingqing Zhou <zhouqq@cs.toronto.edu>,
	pgsql-performance@postgresql.org
Subject: Re: performance problems ... 100 cpu utilization
References: <42D567DB.6000100@works4me.com> <db4l9c$1g4t$1@news.hub.org>
	<42D5DBEB.4010503@works4me.com> <42D5F315.3090301@telogis.com>
	<42D60C2E.3020004@works4me.com> <42D7069B.5090107@telogis.com>
In-Reply-To: <42D7069B.5090107@telogis.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 0528-5, 07/15/2005), Outbound message
X-Antivirus-Status: Clean
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=
X-Spam-Level: 
X-Archive-Number: 200507/218
X-Sequence-Number: 13459

David Mitchell wrote:

> If your table has got into this state, then vacuum analyze won't fix 
> it. You will have to do a vacuum full to get it back to normal, then 
> regularly vacuum (not full) to keep it in good condition. We vacuum 
> our critical tables every 10 minutes to keep them in good nick.


So should I have vacuum run during the load test? At what level of 
updates should it run every ten minutes?

Dennis