In-Reply-To: <cone.1158255415.91768.31944.1000@zoraida.natserv.net>
References: <cone.1158247381.60704.30981.1000@zoraida.natserv.net>
	<56FA8838-6DEA-4505-990D-85D5EDA26243@fastcrypt.com>
	<cone.1158255415.91768.31944.1000@zoraida.natserv.net>
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Content-Transfer-Encoding: 7bit
From: Dave Cramer <pg@fastcrypt.com>
Subject: Re: Vacuums on large busy databases
Date: Thu, 14 Sep 2006 14:43:49 -0400
To: Francisco Reyes <lists@stringsutils.com>

Francisco
On 14-Sep-06, at 1:36 PM, Francisco Reyes wrote:

> Dave Cramer writes:
>
>> What is effective_cache set to ?
>
> Increasing this seems to have helped significantly a web app. Load  
> times seem magnitudes faster.
>
> Increased it to effective_cache_size = 12288 # 96MB
>
> What is a reasonable number?
> I estimate I have at least 1 to 2 GB free of memory.
You are using 6G of memory for something else ?

effective cache should be set to 75% of free memory
>
> Don't want to get too carried away right now with too many  
> changes.. because right now we have very few connections to that  
> database (usually less than 10), but I expect it to go to a norm of  
> 20+.. so need to make sure I won't make changes that will be a  
> problem in that scenario.
>
> So far only see one setting that can be an issue: work_mem so  have  
> it set to only 32768.
>
> ---------------------------(end of  
> broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
>               http://archives.postgresql.org
>