pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dave Cramer <pg@fastcrypt.com>
To: Francisco Reyes <lists@stringsutils.com>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: Vacuums on large busy databases
Date: Thu, 14 Sep 2006 14:43:49 -0400
Message-ID: <470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com> (raw)
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>

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
>




view thread (23+ messages)  latest in thread

Message-ID: <470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com>
Permalink:  ../470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com/
Also on:    postgresql.org/message-id/470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: pg@fastcrypt.com, lists@stringsutils.com
  Subject: Re: Vacuums on large busy databases
  In-Reply-To: <470FED70-B3BA-4B6C-A6B1-DFD8882746B2@fastcrypt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox