RE: Stress testing
One of the better things I have found over time was todo several test.
Most of these involved compiling large amounts of code. Like the linux
kernel source for example.
You may wish to look at the methods for trying to find ways to "break" your
ram. Some of these may include things like.
Extract 4 kernel sources to disk and using diff to compare them. If you get
a difference you know somebody is badly wrong ;)
James
> -----Original Message-----
> From: John Miller [mailto:jmiller@thecsl.org]
> Sent: 12 October 2006 23:24
> To: debian-isp@lists.debian.org
> Subject: Stress testing
>
> We're getting ready to christen a new server (ok, a used Gateway 930 P3,
> 256MB ram) and are leaning toward using the stress package to do stress
> testing, since multiple tests can be run with one command and a timeout
> feature is built-in. Does anyone have advice to the contrary/horror
> stories about the stress tool?
>
>
> --
> To UNSUBSCRIBE, email to debian-isp-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
Reply to: