Date: Wed, 9 Nov 2005 20:07:52 -0300
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Ron Peacetree <rjpeace@earthlink.net>
Cc: Yves Vindevogel <yves.vindevogel@implements.be>,
	pgsql-performance@postgresql.org
Subject: Re: Some help on buffers and other performance tricks
Message-ID: <20051109230752.GC8230@surnet.cl>
Mail-Followup-To: Ron Peacetree <rjpeace@earthlink.net>,
	Yves Vindevogel <yves.vindevogel@implements.be>,
	pgsql-performance@postgresql.org
References: 
 <17035565.1131571489652.JavaMail.root@elwamui-hound.atl.sa.earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <17035565.1131571489652.JavaMail.root@elwamui-hound.atl.sa.earthlink.net>
User-Agent: Mutt/1.5.10i

Ron Peacetree wrote:
> 0= Optimize your schema to be a tight as possible.  Your goal is to give yourself the maximum chance that everything you want to work on is in RAM when you need it.
> 1= Upgrade your RAM to as much as you can possibly strain to afford.  4GB at least.  It's that important.
> 2= If the _entire_ DB does not fit in RAM after upgrading your RAM, the next step is making sure your HD IO subsystem is adequate to your needs.
> 3= Read the various pg tuning docs that are available and Do The Right Thing.
> 4= If performance is still not acceptable, then it's time to drill down into what specific actions/queries are problems.
> If you get to here and the entire DBMS is still not close to acceptable, your fundamental assumptions have to be re-examined.

IMHO you should really be examining your queries _before_ you do any
investment in hardware, because later those may prove unnecessary.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.