New Multi-Threaded Pi Program - Faster than SuperPi and PiFast

[bonis62]

Is this a mis-post? Since it doesn't seem relevant to this thread. Or any sort of digit-crunching for that matter...

PrimeCores is written in assembler ( 85M in 11 secs at 3.2 GHz ) and does not use
advanced mathematical routine therefore fully
compatible with older processors,
the problem of using advanced mathematics is a bottleneck more than help, the good is writing custom advanced math routine that run on all processors,
for benchmarks the compatibility is crucial,
at least I think so.

[poke349]

PrimeCores is written in assembler ( 85M in 11 secs at 3.2 GHz ) and does not use
advanced mathematical routine therefore fully
compatible with older processors,
the problem of using advanced mathematics is a bottleneck more than help, the good is writing custom advanced math that run on all processors,
for benchmarks the compatibility is crucial,
at least I think so.

uh...

PrimeCores finds prime numbers. It has nothing to do with Pi.

y-cruncher is fully compatible with older processors. It just won't be as fast.

In my opinion, the true benchmark is one that adapts to the processor that it's running on by utilizing all special features it has. (Otherwise, why have those special features in the first place?)

Also, y-cruncher wasn't originally written for benchmarking.
It was done for a completely different purpose and later converted into a benchmark.

[bonis62]

uh...

PrimeCores finds prime numbers. It has nothing to do with Pi.

y-cruncher is fully compatible with older processors. It just won't be as fast.

In my opinion, the true benchmark is one that adapts to the processor that it's running on by utilizing all special features it has. (Otherwise, why have those special features in the first place?)

Also, y-cruncher wasn't originally written for benchmarking.
It was done for a completely different purpose and later converted into a benchmark.

if the code performs different operations for different CPU ,
you dont have a true benchmark, you have a simple test.

PI use floating point unit , Prime use integer unit,

I do not want put this into question,
do not speed race,
however, are convinced that a benchmark should run with the same (identical) code on many CPUs to be true benchmark.

[poke349]

if the code performs different operations for different CPU ,
you dont have a true benchmark, you have a simple test.

PI use floating point unit , Prime use integer unit,

I do not want put this into question,
do not speed race,
however, are convinced that a benchmark should run with the same (identical) code on many CPUs to be true benchmark.

Everyone has different views on what a benchmark should be.
Some believe that you should run identical code on all processors.
That's what SuperPi is for.

On the other hand:
If code A runs faster on processor A, and code B runs faster on processor B.
Then I have no problem with benchmarking A on A and B on B if they do the same task.
This is what y-cruncher is. It is meant to be a different kind of benchmark.

Take your pick.


I'm not a fan of crippling processors by not using their features - since that hides their true potential.
It's just like having a street race: If one car has nitrous, why should you ban the driver from using it? It hides its true potential.


EDIT:
Pi doesn't just use floating-point. y-cruncher uses both, floating-point and integer.

Though the ratios of how much of each will vary depending on what system you run it on.
On Intel processors, it uses more floating-point.
On AMD processors, it uses more integer. This is because AMD's have a stronger integer unit than Intel's. (in the context of this program)

[bonis62]

Everyone has different views on what a benchmark should be.
Some believe that you should run identical code on all processors.
That's what SuperPi is for.

On the other hand:
If code A runs faster on processor A, and code B runs faster on processor B.
Then I have no problem with benchmarking A on A and B on B if they do the same task.
This is what y-cruncher is. It is meant to be a different kind of benchmark.

Take your pick.


I'm not a fan of crippling processors by not using their features - since that hides their true potential.
It's just like having a street race: If one car has nitrous, why should you ban the driver from using it? It hides its true potential.


EDIT:
Pi doesn't just use floating-point. y-cruncher uses both, floating-point and integer.

Though the ratios of how much of each will vary depending on what system you run it on.
On Intel processors, it uses more floating-point.
On AMD processors, it uses more integer. This is because AMD's have a stronger integer unit than Intel's. (in the context of this program)

I'm not a fan of crippling processors by not using their features - since that hides their true potential.
It's just like having a street race: If one car has nitrous, why should you ban the driver from using it? It hides its true potential.


in this case i am in full agreement with you.

[Dodgexander]

Thanks for this! I've been using it to stress test my AMD Athlon x750k. Every other test I throw at it passes but the HNT test of Y-Cruncher. It represents CPU+Cache+Memory...but what to tweak to get it to pass this test?

[poke349]

Thanks for this! I've been using it to stress test my AMD Athlon x750k. Every other test I throw at it passes but the HNT test of Y-Cruncher. It represents CPU+Cache+Memory...but what to tweak to get it to pass this test?

No idea. And there's no real way to tell what it breaks on. If none of the other tests reveal the problem, then I guess it's trial-and-error with the OC settings.