Moo Runtimes

[Fire$torm]

I was looking at my completed tasks on Moo's site and discovered some HUGE variation in run times. From a low of 2,300+ sec. to over 13,000+ sec. And the amount of time varies by date.

Nexus (My Desktop):
ID#- 297
List: Completed Tasks

Clocks
CPU: 2.8Ghz (Stock)
ATI 5830: GPU = 950Mhz / MEM = 900Mhz

Projects:
WUProp
FreeHal
MooWrap
PG-PPS (Sieve)
YoYo (Now set to NNT)
Aqua

Any ideas?

Note: I just up'd the 5830 clocks to 1000/1000 (Which MW did not like).

Edit: I put Odin (w/2x 4850) on Moo a short time ago and it completed its first wu in 4,141.21 sec.

4850 clocks: GPU = 700Mhz / MEM = 650

2nd Edit: WUProp Data on ATI Hd 5830 here.

[dan]

Do you have one free core that is doing nothing. I've seen the same when I have all my cores working on a CPU task. So on my i7 I have 75% as the setting for "On multi-core systems use at most". With MOO it then runs 100% of the cpu.

Dan

[Bryan]

F$, there are several things with Moo.

1. The time shown in the "Run Time" may or may not be accurate. On single GPU systems I've found it to be close on dual GPU it may or may not be depending on the system.
2. To get accuracte run time you have to open the wu record "Task" and subtract start time from end time.
3. On a single GPU you need to reserve a thread for Moo. On a dual GPU you need to reserve a FULL CORE.
4. You are running your wu on "core 0". On all my ATIs systems it is MUCH MUCH better to run on "Core 3". You set that in project preferences.

You can run a benchmark that will show you how it will perform on each of your cores. Then use that to select the correct "core" in prefernces.

1, Stop BOINC
2. Call up the command prompt.
3. Type in the path name of the executable "dnetc)1.02_windows_intelx86_ati14.exe -bench". So it will be something like C:\program data\boinc\project\moo wrap\dnetc.... . exe -bench
4. Hit enter.

The program will run and show you the speed of each core on your processor (relative only to Moo). In Project Prefernces that is the one you want to use. Makes a BIG BIG BIG difference in credits.

If you do a search on the Moo forums using the executable name you should be able to find the procedure.

[Fire$torm]

First, thanks for the feedback.

Since the system in question is my desktop I have BM set to use at most 75% of processors. I tried running the -bench switch with dnetc_1.02_windows_intelx86__ati14.exe but no go. Then I tried the switch on dnetc518-win32-x86-stream.exe, Success!!!

dnetc v2.9109-518-GTR-10092921 for ATI Stream on Win32 (WindowsNT 6.1).
Please provide the *entire* version descriptor when submitting bug reports.
The distributed.net bug report pages are at http://bugs.distributed.net/

[Jul 06 16:39:06 UTC] RC5-72: using core #0 (IL 4-pipe c).
[Jul 06 16:39:11 UTC] RC5-72: Benchmark for core #0 (IL 4-pipe c)
0.00:00:02.77 [1,600,863,234 keys/sec]
[Jul 06 16:39:12 UTC] RC5-72: using core #1 (IL 4-pipe c alt).
[Jul 06 16:39:19 UTC] RC5-72: Benchmark for core #1 (IL 4-pipe c alt)
0.00:00:04.75 [920,051,200 keys/sec]
[Jul 06 16:39:19 UTC] RC5-72: using core #2 (IL 4-pipe 2 threads).
[Jul 06 16:39:25 UTC] RC5-72: Benchmark for core #2 (IL 4-pipe 2 threads)
0.00:00:03.38 [1,332,476,140 keys/sec]
[Jul 06 16:39:25 UTC] RC5-72: using core #3 (IL 4-pipe cs-1).
[Jul 06 16:39:30 UTC] RC5-72: Benchmark for core #3 (IL 4-pipe cs-1)
0.00:00:02.77 [1,613,737,911 keys/sec]
[Jul 06 16:39:30 UTC] RC5-72 benchmark summary :
Default core : #0 (IL 4-pipe c)
Fastest core : #3 (IL 4-pipe cs-1)
[Jul 06 16:39:30 UTC] Core #3 is marginally faster than the default core.
Testing variability might lead to pick one or the other.

I changed the project preferences on the Moo site so now its wait and see....

F$

[Bryan]

See what happens when you listen to an old guy! I thought it was the ati executable but it has been along time since I did that. I'm glad you figured it out!

[Fire$torm]

See what happens when you listen to an old guy! I thought it was the ati executable but it has been along time since I did that. I'm glad you figured it out!

Hahaha Very funny At least you got me pointed in the right direction, so thanks.

Just to let you know, a couple of people posted the same suggestion on the Moo forum. So your not alone

Good news. It worked. The elapsed time shown in BOINC Manager dropped to under 40 minutes.

I should have realized something was off much earlier because the 5830 temps were around 59C before the change. Now it sits between 68~70C. Of course now my room is slightly warmer..........

Also, I had to drop the 5830 clocks back to its previous settings. Windows was acting a little funny and when I tried playing World of Tanks I started getting VPU recovery errors.
I may try updating CCC but I am leery of what AMD has been putting out lately.

Anyhow, thanks again for the help.

F$