Moo How-To: One WU per GPU on multi-GPU systems

[Fire$torm]

This info was originally post in the MooWrap forums (Here)

Thats what Mikey pointed you at, that app_info puts one per gpu.

This is the one I am using with 2x5970s, they run one Moo WU per GPU

<app_info>
<app>
<name>dnetc</name>
<user_friendly_name>Distributed.net Client</user_friendly_name>
</app>
<file_info>
<name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc518-win32-x86-stream.exe</name>
<executable/>
</file_info>
<file_info>
<name>dnetc-gpu-1.3.ini</name>
</file_info>
<file_info>
<name>job-ati14-1.00.xml</name>
</file_info>
<app_version>
<app_name>dnetc</app_name>
<version_num>103</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.1</avg_ncpus>
<max_ncpus>0.5</max_ncpus>
<plan_class>ati14</plan_class>
<flops>1157115231469.729200</flops>
<file_ref>
<file_name>dnetc_wrapper_1.3_windows_intelx86__ati14.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>dnetc518-win32-x86-stream.exe</file_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>dnetc-gpu-1.3.ini</file_name>
<open_name>dnetc.ini</open_name>
<copy_file/>
</file_ref>
<file_ref>
<file_name>job-ati14-1.00.xml</file_name>
<open_name>job.xml</open_name>
<copy_file/>
</file_ref>
<coproc>
<type>ATI</type>
<count>1</count>
</coproc>
</app_version>
</app_info>

Create it inside Notepad (no other editor - use Notepad), and save file as a txt format file called app_info.xml, into the Moo Project Directory. Dont forget to run down the cache before using it else you will trash existing WUs. BAM must be closed down and restarted for the app_info to take effect.

EDIT:
In an app_info, the part that contrrols number of WUs running on the gpu is this bit:

<coproc>
<type>ATI</type>
<count>1</count>
</coproc>

A count of one means one per GPU. If it was put as 0.5, it would be 2 per GPU .... and so on, so for example(s)

Count of ...

1 is 1 per GPU
0.5 is two per GPU
0.33 is three per GPU
0.25 is 4 per GPU.

Do the Maths you'll get the idea

(Dont run more than two Moo WU per GPU, utterly pointless, just creates other issues for zero purpose, and usually one per GPU in a multi GPU setup solves the fragmentation / utilisation problem.)

Watch the heat carefully when first starting this, expect to have to downclock GPUs by about 30 on previous setting to keep heat under control - more work flying around, hence the need to reduce GPU speed slighly to compensate - be careful ... you will overheat if you dont watch this the first time you use the app_info.

Regards
Zy

[Al]

It's been a long time since I could get Moo! to run on what little ATI hardware I currently have. I bought a pristine 5970 (dual gpu) for really cheap on ebay and once again, nothing but comp errors. I did a clean sweep of Moo! and started running the stock app with no app_config and it's running one wu/gpu and no errors. Maybe I was trying to make it too difficult or else something changed. Anyway, I'm now looking to take Moo! to 100 million with about 50 million to go.

[John P. Myers]

I ran some MOO! on my R9 295 X2 (dual GPU) last night. WUs were completing on average of 2 every 15 minutes. One WU/GPU and no app_config here either. http://<br /> http://moowrap.net/res...?hostid=453744

[Al]

I ran some MOO! on my R9 295 X2 (dual GPU) last night. WUs were completing on average of 2 every 15 minutes. One WU/GPU and no app_config here either. http://moowrap.net/results.php?userid=1661

I wish mine were that fast, but it is old tech. I also had to downclock a bit and drop the volts to keep it cool enough to make me happy. WUs are running a little over double yours.

[John P. Myers]

http://moowrap.net/results.php?hostid=453744 saw i had the wrong link. Fixed and ran some more. This computer is in a mini tower case. Space is tight making it tougher to keep the GPU at 65C or lower so it won't downclock itself. I like a challenge More work to do still. Temps were 73C last night which is down from 74C the previous night.