From: Gregory Stark <stark@enterprisedb.com>
To: "Marc Mamin" <M.Mamin@intershop.de>
Cc: <pgsql-performance@postgresql.org>
Subject: Re: Postgres configuration for 64 CPUs, 128 GB RAM...
In-Reply-To: 
 <CA896D7906BF224F8A6D74A1B7E54AB301750B12@JENMAIL01.ad.intershop.net>
	(Marc Mamin's message of "Tue, 17 Jul 2007 16:10:30 +0200")
Organization: EnterpriseDB
References: 
 <CA896D7906BF224F8A6D74A1B7E54AB301750B12@JENMAIL01.ad.intershop.net>
Date: Tue, 17 Jul 2007 17:18:28 +0100
Message-ID: <877iozrokr.fsf@oxford.xeocode.com>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


"Marc Mamin" <M.Mamin@intershop.de> writes:

> We have the oppotunity to benchmark our application on a large server. I
> have to prepare the Postgres configuration and I'd appreciate some
> comments on it as I am not experienced with servers of such a scale.
> Moreover the configuration should be fail-proof as I won't be able to
> attend the tests. 

I really think that's a recipe for disaster. Even on a regular machine you
need to treat tuning as an on-going feedback process. There's no such thing as
a fail-proof configuration since every application is different.

On an exotic machine like this you're going to run into unique problems that
nobody here can anticipate with certainty.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com