• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Multi Core Pi v2.000

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Seems a bit more consistent this time.

66gjdz.jpg


2500k @ 4.7ghz
 
It's not terribly significant, but my E5472s are running at stock speed. I do not know why 3003 was reported, a whopping 1/10% overclock...

Oh, yeah, and there are two of them. I did not see a column for number of CPUs.
 
Last edited:
Wait, didn't we do this once and it was concluded the benchmark was pants?

It appears to be pants for AMD chips, Intel chips seem to behave as expected.


Note the author has recompiled and released the app under the same link without any external indication of having done so.

It now runs as rev 2.101, whereas everyone else generated rev 2.000 results.

You can see the difference in the icon located in the lower-left corner.

edit: wow, he even ninja-edited his own thread to replace the download link with the new file while keeping the download counter untouched and makes absolutely no reference to having deprecated his original software with the newer version. How on earth this guy and his benchmark are allowed to be HWBOT accredited is beyond me. Complete BS.
 
Last edited:
Does the Phenom II just suck at this test? Some Intel chips, a 1000mhz slower finished like 20 seconds faster :hmm:
Anyway this a 975 @ 4.0ghz
MultiCorePIScreenShot.jpeg
 
It appears to be pants for AMD chips, Intel chips seem to behave as expected.



Note the author has recompiled and released the app under the same link without any external indication of having done so.

It now runs as rev 2.101, whereas everyone else generated rev 2.000 results.

You can see the difference in the icon located in the lower-left corner.

edit: wow, he even ninja-edited his own thread to replace the download link with the new file while keeping the download counter untouched and makes absolutely no reference to having deprecated his original software with the newer version. How on earth this guy and his benchmark are allowed to be HWBOT accredited is beyond me. Complete BS.

Ran it again, this time on my main rig with 1 core (+HT) at similar clockspeed as my P4.

308a6vq.jpg

LOL, he's now changed it to rev 2.200 🙄
 
LOL, he's now changed it to rev 2.200 🙄

Its possible the benchmarking code itself hasn't changed and only other parts like uploading the result and the visual appearance were updated, but without notes/history its any ones guess.

FWIW, I just ran 2.1 and 2.2 a few times and getting the same time as I was in 2.0.
 
Guys why are you still wasting your time in this crap? Sending an email request to y-crunchers author to release the new version asap would be more beneficial.
 
2.101 He made the output/results encrypted
2.200 He removed the digit slider so it's always 80,000

As seen in this small thread.

Apparently it went from MultiCore PI, to MultiCore Prime, back to MultiCore PI, all of them poorly coded bloatbombs.
 
I honestly don't know what this application does... simplification, but I tried this:
For n As Integer = 0 To 8000000
d += Math.Pow(16, -n) * ((4 / (8 * n + 1)) - (2 / (8 * n + 4)) - (1 / (8 * n + 5)) - (1 / (8 * n + 6)))
Next

Takes about 3 seconds to calculate that... obviously d is limited to: 3.14159265358978~ but I don't see how it's taking 35 seconds for it to calculate 80,000 in "MultiCore PI" and 3 seconds for 8,000,000 iterations in mine.

Something else I discovered, this equation is s**t... if you wanted to do it by hand, or you had some specially built 2048bit CPU awesome... otherwise it's not very accurate.
 
I honestly don't know what this application does... simplification, but I tried this:

Takes about 3 seconds to calculate that... obviously d is limited to: 3.14159265358978~ but I don't see how it's taking 35 seconds for it to calculate 80,000 in "MultiCore PI" and 3 seconds for 8,000,000 iterations in mine.

Something else I discovered, this equation is s**t... if you wanted to do it by hand, or you had some specially built 2048bit CPU awesome... otherwise it's not very accurate.

True. On my 2.3GHz i5-2410M laptop (2C/4T) running a single-threaded calculation in mathematica using the exact same formula that the Multi-core Pi uses, it takes 1.202 seconds to compute 80k digits.

MathematicaPi.png
 
Back
Top