DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
	b=OQh6DhCJaqsZ8LPfXwJof7g/NHdHA38xefuq9X/HD9t8Vl86eowOHrpUfnN3Ta9jwmzvfxRoMvevKFgPbhtf2RMdoEen3qzlAGurrONeYoukgN0GVjxmj6TbK//kc1tNqEIVSEHkLWXOZIrb1D6TLkbkZGAl6s+hbovJxpjENBk=
Message-ID: <88daf38c0705220645n3f37c975he2214f4d514b76b1@mail.gmail.com>
Date: Tue, 22 May 2007 15:45:25 +0200
From: "Alexander Staubo" <alex@purefiction.net>
To: "Stephane Bailliez" <sbailliez@gmail.com>
Subject: Re: Tips & Tricks for validating hardware/os
Cc: pgsql-performance@postgresql.org
In-Reply-To: <4652EBC5.3090802@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <4652EBC5.3090802@gmail.com>

On 5/22/07, Stephane Bailliez <sbailliez@gmail.com> wrote:
> Out of curiosity, can anyone share his tips & tricks to validate a
> machine before labelling it as 'ready to use postgres - you probably
> won't trash my data today' ?
> I'm looking for a way to stress test components especially kernel/disk
> to have confidence > 0 that I can use postgres on top of it.
>
> Any secret trick is welcome (beside the memtest one :)

Compile the Linux kernel -- it's a pretty decent stress test.

You could run pgbench, which comes with PostgreSQL (as part of the
contrib package). Give a database size that's larger than the amount
of physical memory in the box.

Alexander.