bdzyub DeleteThis @gmail.com wrote:
> ok, so what torture test should I perform: the blend or the in place
> large FFT?
>
Blend is fine. It does a little of everything.
Small FFTs tend to stay in cache. This stresses the CPU, heats it up,
tests your cooling and your CPU.
Large FFTs are larger than the cache. So tend to stay more in system
memory, results in some transfers from main memory. More of memory
gets tested that way.
If you want finer control of Prime95, you can run the mersenne.org version
under Linux. As long as each copy of Prime95 under Linux, is given its own
directory, you can run multiple copies. For example, I've run four copies
on my P4 system (with Hyperthreading, my processor looks like two cores). I
assign a different amount of RAM to each program, and each program executes
the blend. But with the different amounts of RAM, the programs cannot use
the same test pattern. I find that is a pretty good test.
Note that Prime95 style testing, doesn't say "location X in memory is bad".
It reports a rounding error, but without details. By using the Linux testing
method, and launching multiple copies, you can give each copy its own section
of RAM to test, and I have found consistent failures that way. (For example,
with four test programs, the third program always gave errors, so the section
of memory I gave it, must have a bad location in it. Obviously, the order of
execution, and the size of memory allocation, must be consistent from run to
run, to note something like that. A reboot between runs, will put the memory
allocation system in a consistent state.)
Paul
>> Stay informed about: memtest86+ errors