About the app_info.xml file and using it, I'm still missing why some machines are successful and other machines are not .

My understanding is that the use of an app_info.xml can not but result into the so-called 'anonymous platform'; and while a number of people have used the app_info.xml file with success here at WCG, it is not clear if WCG officially supports 'anonymous platform'. The app_info.xml files I have seen here at WCG essentially mirror what WCG officially has and it becomes a matter of writing into that app_info.xml file what WCG officially runs plus some configs for machines (like running multiple HCC-GPU-WUs) -- and as such, there is, in effect, nothing 'anonymous' about the data in those app_info.xml files that are used (or recommended by crunchers for use) at WCG. I'm thus wondering why the added machine configs in an app_info.xml file could not be made to be handled by the old reliable cc_config.xml . Perhaps in the near future?
;
; edit1_2012.11.07We.1334utc > presentation improvements.
;

I was using this app_info, it was working (2x tasks using the GPU, 2x tasks using CPU only), but then by the morning everything had stopped.

I'm not sure when it stopped during the night.

Any ideas?

-- Craig

<app_info>
   <app>
      <name>hcc1</name>
      <user_friendly_name>XtremeSystems Crunches Cancer</user_friendly_name>
   </app>
   <app>
      <name>gfam</name>
      <user_friendly_name>XtremeSystems Fights Malaria</user_friendly_name>
   </app>


   <file_info>
      <name>wcg_hcc1_img_6.56_windows_intelx86__nvidia_hcc1</name>
      <executable/> 
   </file_info>
   <file_info>
      <name>hcckernel.cl.6.56</name>
      <executable/>
   </file_info>

   <file_info>
      <name>wcg_hcc1_img_6.56_windows_intelx86</name>
      <executable/>
   </file_info>

   <file_info>
      <name>wcgrid_gfam_vina_6.12_windows_x86_64</name>
      <executable/>
   </file>
   <file_info>
      <name>wcgrid_gfam_vina_prod_x86_64.exe.6.12</name>
      <executable/>
   </file>

   <app_version>
      <app_name>hcc1</app_name>
      <version_num>656</version_num>
      <platform>windows_intelx86</platform>
      <plan_class>nvidia_hcc1</plan_class>
      <avg_ncpus>1.000000</avg_ncpus>
      <max_ncpus>0.750000</max_ncpus>
      <coproc>
         <type>CUDA</type>
         <count>0.500000</count>
      </coproc>
      <file_ref>
          <file_name>wcg_hcc1_img_6.56_windows_intelx86__nvidia_hcc1</file_name>
          <main_program/>
      </file_ref>
      <file_ref>
         <file_name>hcckernel.cl.6.56</file_name>
         <open_name>hcckernel.cl</open_name>
      </file_ref>
   </app_version>

   <app_version>
      <app_name>hcc1</app_name>
      <version_num>656</version_num>
      <platform>windows_intelx86</platform>
      <avg_ncpus>1.000000</avg_ncpus>
      <max_ncpus>1.000000</max_ncpus>
      <flops>3231932486.733310</flops>
      <api_version>6.13.0</api_version>
      <file_ref>
         <file_name>wcg_hcc1_img_6.56_windows_intelx86</file_name>
         <main_program/>
      </file_ref>
   </app_version>


<app_version>
    <app_name>gfam</app_name>
    <version_num>612</version_num>
    <platform>windows_x86_64</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3868351853.053741</flops>
    <api_version>7.1.0</api_version>
    <file_ref>
        <file_name>wcgrid_gfam_vina_6.12_windows_x86_64</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>wcgrid_gfam_vina_prod_x86_64.exe.6.12</file_name>
        <open_name>AutoDockVina64.exe</open_name>
    </file_ref>
</app_version>

<app_version>
    <app_name>gfam</app_name>
    <version_num>612</version_num>
    <platform>windows_intelx86</platform>
    <avg_ncpus>1.000000</avg_ncpus>
    <max_ncpus>1.000000</max_ncpus>
    <flops>3347548492.458962</flops>
    <api_version>7.1.0</api_version>
    <file_ref>
        <file_name>wcgrid_gfam_vina_6.12_windows_x86_64</file_name>
        <main_program/>
    </file_ref>
    <file_ref>
        <file_name>wcgrid_gfam_vina_prod_x86_64.exe.6.12</file_name>
        <open_name>AutoDockVina64.exe</open_name>
    </file_ref>
</app_version>

</app_info>

7.x is needed for Win8 installations.

-- Craig

Have a question too. It doesnt matter me to much, but perhaps someone knows why ^^

Im running 4 WUs at once on a HD7950 on a P5K Mainboard with 2GB DDR2-800 Dual Channel and a Q6600 CPU. Running one WU gpu load is 70%, with second its 80% but with 3 and 4 wus it stays at max 80%. I wonder what the bottleneck is when every WU gets his own physical CPU Core. is it because no PCIe 3.0 slot or something?

i know it uses CPU too, but it using cpu at beginning and on the end ;) but between it using 80% only, i mean the progress between 0,001% and 99,415. It definite uses only 80% in this phase ^^ I will try more WUs at monday at once because i read it is makeable with a change of avg cpu in appinfo. But im sure it will stay @ 80% ^^