From: PFC <lists@peufeu.com>
To: Alexander Staubo <alex@purefiction.net>
To: Stephane Bailliez <sbailliez@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Tips & Tricks for validating hardware/os
Date: Tue, 22 May 2007 15:55:26 +0200
Message-ID: <op.tsqeao0fcigqcu@apollo13> (raw)
In-Reply-To: <88daf38c0705220645n3f37c975he2214f4d514b76b1@mail.gmail.com>
References: <4652EBC5.3090802@gmail.com>
<88daf38c0705220645n3f37c975he2214f4d514b76b1@mail.gmail.com>
>> 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.
That would be running a filesystem benchmark, pulling the plug, then
counting the dead.
http://sr5tech.com/write_back_cache_experiments.htm
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: lists@peufeu.com, alex@purefiction.net, sbailliez@gmail.com
Subject: Re: Tips & Tricks for validating hardware/os
In-Reply-To: <op.tsqeao0fcigqcu@apollo13>
* 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