Re: Server testing.

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Server testing.
Date: 2002-12-17 15:40:19
Message-ID: Pine.LNX.4.33.0212170837140.24291-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, 17 Dec 2002, Lincoln Yeoh wrote:

> I used the cpuburn program too ( http://users.ev1.net/~redelm/ ). It REALLY
> heats up the processor - interesting to watch the +5 volt immediately drop
> significantly (using healthd -d). The other voltages also change accordingly.
>
> The test doesn't touch files unlike a kernel recompile, so if you find you
> have a flaky system there's a lower chance of a corrupted filesystem.
>
> Plus compiling doesn't put as much load on my CPU - the +5V doesn't drop as
> much. I suspect there's not as much FPU access whilst compiling. And the
> FPU units are significant power consumers.
>
> Not sure what to use for testing P4s tho (there isn't a cpuburn test
> specifically for P4s). I'm using an Athlon XP so I use the burnK7 program.

I've used quake II as a good CPU cooker as well. any good FPS (First
Person Shooter) usually cranks up the heat on the CPU. Plus it is fun to
leave Quake on your new dual AMD 2400 MP system in the server room in demo
mode for a week or so to burn it in.

Of course, what we're all saying is how to beat your server like a mule
BEFORE it goes into production. :-)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Shridhar Daithankar 2002-12-17 16:03:21 Re: Server testing.
Previous Message Ericson Smith 2002-12-17 15:19:43 7.3 Prepared statements