Date: Tue, 2 Mar 2004 14:32:42 -0500 From: Kenneth Culver <culverk@sweetdreamsracing.biz> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Colin Percival <colin.percival@wadham.ox.ac.uk> Subject: Re: detecting overheating processors? Message-ID: <20040302143242.sc88g4ogcw4wcwo0@www.sweetdreamsracing.biz> In-Reply-To: <81725.1078252607@critter.freebsd.dk> References: <81725.1078252607@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Poul-Henning Kamp <phk@phk.freebsd.dk>: > In message <1942228052.20040302193211@andric.com>, Dimitry Andric writes: > >>> I would prefer to have a program called "stress" which could be run >>> at any time to test hardware. >> >> It's called "make buildworld". ;) > > In fact it isn't (anymore). > > I've seen modern hardware run buildworld for days, but explode on > scientific FP work in a few minutes. > > It used to be the case that buildworld would stress a CPU, but with > all the specialty circuitry put into CPUs these days, buildworld > probably ends up using the MMX and SSE extension silicon as a > heatsink. > > A real stress-test would be something which engages bus-interface, > integer, floating point and preferably any "extensions" as well. One decent benchmark for me has been encoding from mpeg2 to mpeg4 using mencoder. If you run one process using MMX/SSE/whatever and the other forced to normal FP, you can test all the different execution units at once doing this. I've had times where I had my memory timings set too agressively in BIOS, where make buildworld wouldn't cause any problems, but using a couple of mencoders at once along with a buildworld would make the machine die. :-) Ken
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040302143242.sc88g4ogcw4wcwo0>