New Prime95

[umccullough]

<sigh>

Guess I'll have to update the Haiku port(s) again...

[imwithid]

Wow, I just upgraded one of my machines with Prime95 26.4 and what a boost! From .077 to .055 on a Core2 4300 @ 1.8Ghz (relatively clean install). That's almost a 30% boost! I may be paranoid to want to finish my workers before upgrading but such an increase in performance is too tempting. This is far better than the 3-5% average improvement in the 25.x series of updates. I've got a Quad Core AMD Phenom that I'm curious how well it will perform after these updates (perhaps none, but worth a try).

[tqft]

The current download from seventeenorbust.com for linux appears to be for 263 dated 18 Oct 2010 - should I wait for 264 or upgrade now?

[Joe O]

I haven't sent Louis the updated packages to post. Do you need the package or are you already running Prime95? If you are already running Prime95 then just download the new executable. If you are just starting, then download the package, and replace the executable before startiing. If you are just starting then please make sure that your userid is correct in the prime.txt file so that you will get credit for your work.

[Cowering]

I was setting up prime95 for a friend. His machine is a Pentium-D (true dual core) OCed to 3.2GHZ. It runs perfectly, but... worker thread #1 is reported as a 'Pentium 4-type3' in the prime95 output window. worker thread #2 is reported as a 'Core2-type3'. Thread 2 is running iterations about 20% faster than thread 1, when both cores are just idling. Is this a detection error? Can I somehow force thread 1 into Core2 mode for some extra speed?

Go TeamRetro!

[prime95]

worker thread #1 is reported as a 'Pentium 4-type3' in the prime95 output window. worker thread #2 is reported as a 'Core2-type3'.

This is probably normal. On a Pentium 4, some FFT lengths are actually faster using FFTs optimized for the Core 2. Prime95 knows this and selects the right one accordingly. Admittedly, the "Core2 type 3" wording is poor/misleading.

I'll bet worker #1 and worker #2 are using different FFT lengths. If you can tell me which FFT lengths the two workers are using and if this is 32-bit or 64-bit prime95, then I can tell you if this is a bug or a feature.

I also own a Pentium D which I benchmarked to pick the fastest FFT implementation for each FFT length.