Excluded by a SPAM filter + reposted, by the list owner's request :-)
Tony.
--
Dr. A.J.Travis, University of Aberdeen, Rowett Institute of Nutrition
and Health, Greenburn Road, Bucksburn, Aberdeen AB21 9SB, Scotland, UK
tel +44(0)1224 712751, fax +44(0)1224 716687, http://www.rowett.ac.uk
mailto:[email protected], http://bioinformatics.rri.sari.ac.uk/~ajt
--- Begin Message ---
Joe Landman wrote:
> Mark Hahn wrote:
>
>> - do you have or know of a good exerciser for testing ECC's? yes, I
>> know about memtest86, but I'm more curious about a load that could be
>> run under
>> linux. my thinking is that ecc's are triggered by bad reads, so something
>> which allocates all memory and then continually reads it would be best.
>
> Thats memtest. We found it doesn't trigger MCEs, and often will report
> a system as good, that once it leaves the lab, generates lots of MCEs on
> customer code. So we run specific codes (GAMESS and others) to burn in
> the machine.
Hello, Joe.
Do you mean Memtester?
http://pyropus.ca/software/memtester/
I stress test non-ECC memory in our compute nodes by running 100
memtester passes on 128MB of the available RAM. This test often reveals
problems in the memory management system that an initial 24h memtest86+
burn-in on all the memory on a node doesn't detect. Memtester is a more
empirical stress test than Memtest86+, but I believe it's more realistic
and I chose 128MB as typical for the type of jobs running on our system.
Bye,
Tony.
--
Dr. A.J.Travis, University of Aberdeen, Rowett Institute of Nutrition
and Health, Greenburn Road, Bucksburn, Aberdeen AB21 9SB, Scotland, UK
tel +44(0)1224 712751, fax +44(0)1224 716687, http://www.rowett.ac.uk
mailto:[email protected], http://bioinformatics.rri.sari.ac.uk/~ajt
--- End Message ---
_______________________________________________
Beowulf mailing list, [email protected]
To change your subscription (digest mode or unsubscribe) visit
http://www.beowulf.org/mailman/listinfo/beowulf
