wPrime Benchmark

[stasio]

wPrime Benchmark 2.01

-Version 2.01 updates the hardware detection method to CPUz version 1.53 (see cpuid.com) to improve support for the latest processors.

[jmke]

does it revert performance behavior back to v1.55 level though?

[wwwww]

Still up at v2.00 levels, there's very little difference between v1.55 and v2.00, basically I removed some compile optimizations because these were causing the variances in the performance between compiles, there was no way to keep consistent scores between compiles using the v1.xx calculation module. The only solution was to redo the calculation module and compensate for difference in performance as best possible, they should be roughly equal for modern day CPUs, with v2.xx being faster than v1.xx for older CPUs. v2.xx will always have consistent performance between versions, that's why I prefer to continue with it.

[Leeghoofd]

Gonna give this one a spin, thx for the heads up Stasio and wwwwwwwwwww

[zalbard]

v2.xx will always have consistent performance between versions, that's why I prefer to continue with it.

It's working very well for me, hope it'll become a standard soon.

[stasio]

wPrime Benchmark 2.02

-corrected a performance issue in v2.01
-submissions from earlier versions are no longer being accepted

[stasio]

wPrime Benchmark 2.03

We've just found that wPrime is indeed hanging on certain systems (confirmed on a fresh install of Windows Vista). It appears as though Vista would assign a different temporary directory to wPrime from CPUz (probably because wPrime was run as Admin). Consequently wPrime never found the CPUz output file and waited.

We've corrected this in version 2.03.

[stasio]

wPrime Benchmark 2.05

http://download.wprime.net/wPrime205.zip

-upgraded CPUz to version 1.58

[FlanK3r]

some diferences in performance?

[mattkosem]

wPrime Benchmark 2.05

http://download.wprime.net/wPrime205.zip

-upgraded CPUz to version 1.58

I get "Unexpected error; quitting" when I try to run this on my system. It's running win 7 x64 on a Llano if it makes a difference.

--Matt

[Sailindawg]

Does version 2.05 detect a 2600K? I've tried benching my 2600K + Asrock Ex4 with version 2.05 and it doesn't seem to detect my hardware. I can run the benchmark, but W-prime does not detect my hardware. It just sits and spins. Any ideas?

[Olivon]

Does version 2.05 detect a 2600K? I've tried benching my 2600K + Asrock Ex4 with version 2.05 and it doesn't seem to detect my hardware. I can run the benchmark, but W-prime does not detect my hardware. It just sits and spins. Any ideas?

At launch, keep Shift key pushed ...

[Sailindawg]

Umm.....yes, I understand how to override the hardware scan, but does the hardware scan work? particularly with Sandy Bridge.

[stasio]

wPrime Benchmark 2.06

http://download.wprime.net/wPrime206.zip

[wwwww]

The hardware scan should work with Sandy Bridge now (in 2.06).

[stasio]

wPrime Benchmark 2.07

http://download.wprime.net/wPrime207.zip

Upgraded CPUz to version 1.59
Fixed parsing bug which would miss some DMI information
Added commandline option -run=32M and -run=1024M
Added support for checking processor count
Changed save file format to support processor count data
Made wPrime request Admin privileges when running

[stasio]

wPrime Benchmark 2.08

http://download.wprime.net/wPrime208.zip

Made wPrime console output to the std
Added commandline option -exit=1 to auto quit after completing test

[stasio]

wPrime Benchmark 2.09

http://downloads.putme.net/wPrime209.zip

Added link field in wPrime submission
Upgraded CPUz to 1.60