Results 1 to 5 of 5

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

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Past Administrator
    Fire$torm's Avatar
    Join Date
    October 13th, 2010
    Location
    In the Big City
    Posts
    7,938

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

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

    Quote Originally Posted by Zydor (MooWrap Forum)
    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
    Code:
    <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>
    Quote Originally Posted by Zydor (MooWrap Forum)
    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
    Last edited by Fire$torm; 07-22-12 at 04:06 PM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •