Who has a bored cluster? REV 2.0

[UncleAl]

Let's cut to the chase,

http://www.mazepath.com/uncleal/uncleal2.zip

That is everything you need for serial timing runs, plus a README file. 272K download. Does your iron outperform an AMD FX-55 at 36 min 4 sec?

[Morally.Corrupted]

I'll grab the file tonight - Will let you know my times ....

[Morally.Corrupted]

Ran the timer on Single unit P4-HL -though for some reason possible due to my own error my data output doen't resemble the sample data provided.

l run it again on the slowest unit for you later

30000.000 10536230484820 0.999999996563450112
30001.000 10537284108460 0.999999994889044989
30002.000 10538337781848 0.999999992353169516

[UncleAl]

The numbers are bang-on, as they should be for a given executable, radius/atoms/CHI. What was the difference in timestamps between time1.txt and time2.txt output files? An FX-55 does the second run, the three larger radius points, in 36 min 4 sec. The first file requires a (fractional) second and is only used to set a starting time for the second file.

You don't need an external timer. Merely subtract the two timestamps. That gives better numbers - no other process adding to delays. From README in the ZIP, right at the top of the file,

TIMING RUN: "timer.bat" script file runs executable static file "chibzh" through two radius intervals. No external math libraries are needed. The difference in timestamps is the execution time for the second run for three points: 30,000 A, 30,001 A, and 30,002 A radius. An AMD FX-55 requires 36 min 4 sec.

:8^>)

[alexander]

on nix, you can always use the time command, uncle it records time just prior to execution, and calculates the difference after the execution completion....

try it,

time cat /proc/cpuinfo

eliminates the need for that section of the code all together..... you could also use a var to record unix time prior to execution and then just after the finish, the difference will give you run time in seconds...

[Morally.Corrupted]

I will compare the timestamps tonight and post them for you, I'll also hit a few other boxes with the timer as well too...

[UncleAl]

Thank you! No matter how you do the timing, it is only the timing that matters. Adding another 0.1 log(radius) extension to the graph would require ~63 days in the FX-55. It makes more sense to run in slack time in unused hardware or in a bored cluster. The fitted line may not be perfectly straight. The slight curvature, if any, only shows at large radii.

http://www.mazepath.com/uncleal/bzhdense.png
78 atoms/unit cell, with hydrogens.
http://www.mazepath.com/uncleal/bzdense.png
48 atoms/unit cell, no hydrogens.
The hydrogens matter despite the slower crunch

The payoff is a coin flip. If you contribute - after the experiment is run - either you get an Acknowledgement in the published paper (spacetime is chiral) or we don't tell anybody (no surprises observed). Every physicist knows what the answer must be! A similar question was asked Christmas 1956. On New Year's Day 1957 every physicist who knew what the answer must be was proven wrong,

The Fall of Parity

Question authority.

[Morally.Corrupted]

Ok ran the timer.bat file again on my AMD machine and checked the timestamps on the P4...

P4 -
07:14:30
08:19:29

01:05:01

AMD
21:06:22
21:49:21

00:43:01

[UncleAl]

P4 - 01:05:01
AMD 00:43:01

You can appreciate the need for a bored cluster with the parallel processing version of the program. Is the AMD doing anything for a couple of months? Sigh. I can write up a serial script file for new radii with estimated execution times. A single P4 really isn't up to the task. Intel hafnium CPUs with 45 nm architecure will be interesting.

[Morally.Corrupted]

What I will do I setup the chibzh to run through MPI and see what sort of numbers the cluster itself will generate on the timer.bat file....will post results