PDA

View Full Version : Weird benchmark msg



vaughan
12-16-2008, 12:57 AM
I'm getting this message and I haven't seen it on my other computers. Any ideas how to fix it or if it does any harm?

BOINC v6.4.5
Win XP Pro 64bit SP2
ASUS P5K-E mobo
4GB Corsair Dominator DDR2 1066 RAM
Intel Q6600 @ 2.7GHz
Gigabyte Nvidia 9800GT 512MB
ForceWare 177.79 (according to Riva Tuner 2.21)
GPU temp 60C fan @ 100%

16/12/2008 12:32:00 PM||Running CPU benchmarks
16/12/2008 12:32:00 PM||Suspending computation - running CPU benchmarks
16/12/2008 12:32:32 PM||Integer benchmark ran only 0.875000 sec; ignoring

Ramjet
12-16-2008, 01:06 AM
Have you run any stress tests such as Prime95 with your current OC settings?

AMDave
12-16-2008, 01:13 AM
I'm getting this message and I haven't seen it on my other computers. Any ideas how to fix it or if it does any harm?

BOINC v6.4.5
...
GPU temp 60C fan @ 100%
...
16/12/2008 12:32:32 PM||Integer benchmark ran only 0.875000 sec; ignoring

focussing on the important bits above, you have the latest BOINC version, the GPU is at ideal temp when the fan is at max.

The problem is the benchmark.
This error occurs when BOINC has instructed all wu's to suspend so that it has a clear run at the CPUs, but there is still something running with 'high priority' when the benchmark started.

I suggest you manually suspend all wu's for a moment.
Check nothing is chewing up the CPU/GPU
run a manual benchmark and see if you get the same result

My guess is that one of the work units was really tardy about suspending and had not stopped by the time the benchmark started.

Give it a go and see what happens.

(Don't forget to resume your work units)

AMDave
12-16-2008, 01:21 AM
1st picked up in BOINC 6.2.x where they inserted the "ignore benchmark if run in less than 3 seconds".
http://boinc.berkeley.edu/dev/forum_thread.php?id=2518&nowrap=true#17311

I think this is when they started pushing in the GPGPU code, which would correlate to the GPU feeder process being in a tight loop on the CPU.

In almost all cases the next benchmark runs just fine.

As above, my guess is a tardy wu suspension (eg GPU feeder) OR a non-BOINC process is also slapping the CPU/GPU around at the time the benchmark started.

Jason1478963
12-16-2008, 02:03 AM
I guess i would try throwing out the Intel CPU and replace it with an AMD :p other then that I wouldn't know what else to try.

AMDave
12-16-2008, 05:53 AM
ha ha ha :icon_lol:

15-Love to Jason.

vaughan
12-16-2008, 06:46 AM
Thanks Dave.
LOL Jason - maybe if the Phenom 2 lives up to its hype :icon_wink:

I think it was something else running. New benchmark is:

16/12/2008 6:42:57 PM||Benchmark results:
16/12/2008 6:42:57 PM|| Number of CPUs: 3
16/12/2008 6:42:57 PM|| 2546 floating point MIPS (Whetstone) per CPU
16/12/2008 6:42:57 PM|| 7790 integer MIPS (Dhrystone) per CPU

Note: 3 CPUs as I have Folding GPU client on this box. I paused it to run the BOINC benchmark.