Posts by Sutaru Tsureku

Sutaru Tsureku

• --non-responsive
  
• --gpu-target-frequency N
  
• --gpu-polling-mode N
  
• --gpu-wait-factor N
  
• --process-priority N
  
• --gpu-disable-checkpointing
  

On my both PCs I use currently:
--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0.01 --process-priority 4 --gpu-disable-checkpointing

[and on the/my FuryX: 3 WUs/GPU - GT730: 2 WUs/GPU
At SETI just 1 WU/GPU possible (on FuryX) - if more tasks/GPU simultaneously invalid results or computation errors.]


BTW.
Still with Crimson 15.12 (1912.5 driver included).
From my experiences the 'best' driver so far. Although with a downclock bug on FuryX. Either after a few minutes or a few days one or more VGA cards downclock continuously - just a reboot help.
I tested all (also Beta/Hotfix) up to Crimson 16.3.2 and Crimson 16.7.2 (Hotfix? but WHQL?)
16.3.2 invalid AP results at SETI, 16.7.2 (July/19) frozen VGA cards.


I don't know if this are the 'strongest/fastest' possible settings - and maybe it could be counterproductively...?

Is somewhere an overview with explanation of all possible cmdline settings - and how to set them?
If not, it's possible to do this (maybe sticky thread in Number Crunching)?



This is the currently used app_info.xml file of my FuryX PC (apps like above):

<app_info>
<app>
<name>milkyway_nbody</name>
<user_friendly_name>Milkyway N-Body Sim.</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_1.62_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>162</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_nbody_1.62_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
<user_friendly_name>Milkyway</user_friendly_name>
</app>
<file_info>
<name>milkyway_1.36_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>milkyway_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.17</avg_ncpus>
<max_ncpus>0.17</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0.01 --process-priority 4 --gpu-disable-checkpointing</cmdline>
<coproc>
<type>ATI</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>milkyway_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
<user_friendly_name>Milkyway Sep. (Mod. Fit)</user_friendly_name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>milkyway_separation__modified_fit</name>
</app>
<file_info>
<name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_separation__modified_fit</app_name>
<version_num>136</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.17</avg_ncpus>
<max_ncpus>0.17</max_ncpus>
<plan_class>opencl_ati_101</plan_class>
<cmdline>--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0.01 --process-priority 4 --gpu-disable-checkpointing</cmdline>
<coproc>
<type>ATI</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>milkyway_separation__modified_fit_1.36_windows_x86_64__opencl_ati_101.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>


('milkyway_separation__modified_fit' part(s) still needed, because old resends around.)



The FuryX PC have two Xeon CPUs, 6Cores/12Threads each, but HT off for faster GPU app calculation, so in whole 12 CPU-Cores available.

With this above app_info.xml file entries:
2 CPU-Cores for GPU app support
10 CPU-Cores for CPU tasks

With this settings the whole PC use ~ 1,100 W at the wall plug. But no problem, the PC have a 2,000 W PSU.
At SETI it was ~ 850 W.
The GPU temps are higher (~ + 4 °C) and the (PC-)room hotter - ambient temps currently 38.5 °C. :-(

With this settings, it looks like ~ 10 seconds / GPU task (theoretically).
The tasks last ~ 30 seconds, but then are 3 tasks finished.

It's really a hard work for BOINC to feed the PC with enough tasks for 24/7. :-( and ;-)



If someone have also a FuryX VGA card, you are welcome to write here also in this thread to share your experiences.



Thanks.

Sutaru Tsureku

• --non-responsive
  
• --gpu-target-frequency N
  
• --gpu-polling-mode N
  
• --gpu-wait-factor N
  
• --process-priority N
  
• --gpu-disable-checkpointing
  

On my both PCs I use currently:
--non-responsive --gpu-target-frequency 1 --gpu-polling-mode 0 --gpu-wait-factor 0.01 --process-priority 4 --gpu-disable-checkpointing

[and on the/my FuryX: 3 WUs/GPU - GT730: 2 WUs/GPU]

I don't know if this are the 'strongest/fastest' possible settings - and maybe it could be counterproductively...?

Is somewhere an overview with explanation of all possible cmdline settings - and how to set them?
If not, it's possible to do this (maybe sticky thread in Number Crunching)?


Thanks.

Sutaru Tsureku

Milkyway@home	13.02.2012 23:05:03	update requested by user	
Milkyway@home	13.02.2012 23:05:08	Fetching scheduler list	
Milkyway@home	13.02.2012 23:05:09	Master file download succeeded	
Milkyway@home	13.02.2012 23:05:14	Sending scheduler request: Requested by user.	
Milkyway@home	13.02.2012 23:05:14	Not reporting or requesting tasks	
Milkyway@Home	13.02.2012 23:05:17	Scheduler request completed

Milkyway@Home	13.02.2012 23:25:33	Sending scheduler request: To fetch work.	
Milkyway@Home	13.02.2012 23:25:33	Requesting new tasks for NVIDIA GPU	
Milkyway@Home	13.02.2012 23:25:36	Scheduler request completed: got 1 new tasks	
Milkyway@Home	13.02.2012 23:25:38	Started download of milkyway_separation_1.02_windows_intelx86__opencl_nvidia.exe

Sutaru Tsureku

Milkyway@home	13.02.2012 21:02:40	Sending scheduler request: To fetch work.	
Milkyway@home	13.02.2012 21:02:40	Requesting new tasks for NVIDIA GPU	
Milkyway@home	13.02.2012 21:02:43	Scheduler request failed: HTTP file not found