Date: Wed, 21 Jan 2004 13:38:34 -0500 From: Jeremy Faulkner <gldisater@gldis.ca> To: Joerg Pernfuss <elessar@galgenberg.net> Cc: freebsd-questions@freebsd.org Subject: Re: Using FreeBSD to burn in computers Message-ID: <400EC72A.1020801@gldis.ca> In-Reply-To: <20040121170912.4f1bc946@aragorn> References: <5.2.0.9.0.20040120145720.02132688@mail.auracom.com> <u2soesxxu1n.fsf@gs166.sp.cs.cmu.edu> <20040121170912.4f1bc946@aragorn>
next in thread | previous in thread | raw e-mail | index | archive | help
Joerg Pernfuss wrote: > On 21 Jan 2004 09:20:20 -0500 > Dan Pelleg <daniel+bsd@pelleg.org> wrote: > > >>>[...] >>>b)make world; make world; make world; make world; make world (my >>>idea here is to run make world and make on XFree86 concurrently, >>>thus stressing the system further - I'm not sure if this is a good >>>idea or not, but I'm sure someone will correct me.) >> >> >>Have make start up many compiles in parallel with the -j switch: for >>example "make -j3". My rule of thumb for a most-effective make is 3 >>times the number of processor. You will probably want a higher number >>just so the strain on memory and disk is higher. > > > For his purpose of stress testing the memory: > make -j64 buildkernel > > I use this on dual proc boxes, maybe -j32 is already more than enough > for a single cpu. > > Won't work with less than 128MiByte RAM iirc, but so far I haven't seen > something different that puts that much stress on your memory. > Surviving this two or three times in a row you can label your RAM > `non-faulty'. > > Joerg Or he could just use memtest (ports/sysutils/memtest) -- Jeremy Faulkner http://www.gldis.ca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?400EC72A.1020801>