How to configure v6 AP GPU tasks

Caprio · June 13, 2013, 05:57:38 AM

I only get GPU to work on v7 seti tasks. I would like to get them to work also on v6 AP tasks too. How to get some tasks on? How to configure when GPU/CPU task assignment?

Here is my app_info.xml:

<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>AKv8c_Bb_r1846_winx86_AVXx.txt</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
   <platform>windows_intelx86</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
   <platform>windows_x86_64</platform>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>AKv8c_Bb_r1846_winx86_AVXx.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name>
</file_info>
<file_info>
<name>AstroPulse_Kernels_r1843.cl</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_100</plan_class>
   <cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_100</plan_class>
   <cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_100</plan_class>
   <cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>604</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_100</plan_class>
   <cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>AP6_win_x86_SSE2_OpenCL_NV_r1843.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
<file_ref>
<file_name>AstroPulse_Kernels_r1843.cl</file_name>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE_CPU_r1797.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x86_SSE_CPU.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
   <cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
   <cmdline></cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3.dll</file_name>
</file_ref>
<file_ref>
<file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41zc_win32_cuda50.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_50_35.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
   <platform>windows_intelx86</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
   <platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>0.33</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zc_win32_cuda50.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
     <file_name>cudart32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_50_35.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
</app_info>

Claggy · June 13, 2013, 06:35:19 AM

Quote from: Caprio on June 13, 2013, 05:57:38 AM
I only get GPU to work on v7 seti tasks. I would like to get them to work also on v6 AP tasks too. How to get some tasks on? How to configure when GPU/CPU task assignment?

Link to your host?

Claggy

arkayn · June 13, 2013, 06:42:59 AM

Quote from: Claggy on June 13, 2013, 06:35:19 AM
Quote from: Caprio on June 13, 2013, 05:57:38 AM
I only get GPU to work on v7 seti tasks. I would like to get them to work also on v6 AP tasks too. How to get some tasks on? How to configure when GPU/CPU task assignment?
Link to your host?

Claggy

http://setiathome.berkeley.edu/show_user.php?userid=35523

Claggy · June 13, 2013, 06:56:29 AM

Quote from: arkayn on June 13, 2013, 06:42:59 AM
Quote from: Claggy on June 13, 2013, 06:35:19 AM
Quote from: Caprio on June 13, 2013, 05:57:38 AM
I only get GPU to work on v7 seti tasks. I would like to get them to work also on v6 AP tasks too. How to get some tasks on? How to configure when GPU/CPU task assignment?
Link to your host?

Claggy

http://setiathome.berkeley.edu/show_user.php?userid=35523

But which host is he talking about, on one of them he is running CPU r555, one is on r557 and the other is on r1797, has he actually run the 0.41 Installer and restarted Boinc?

Claggy

William · June 13, 2013, 05:01:57 PM

Caprio, why are you trying to do everything by hand when we have a perfectly working installer v0.41?

hang on that IS an installer app_info.xml

64 bit, MB for CPU, AP for NV CPU, AP for CPU and MB for CPU - all there.

What is your problem Caprio? If you are not getting tasks you might want to recheck that your website settings allow the work you want.
After that it's luck of the draw, but if you want to make sure you have a cache of AP, temporarily disable MB on the website, wait that you have been allocated AP (can take some time) and then reenable MB workftech on the website.

Caprio · June 14, 2013, 01:56:28 AM

Quote
Link to your host?
http://setiathome.berkeley.edu/show_user.php?userid=35523

But which host is he talking about, on one of them he is running CPU r555, one is on r557 and the other is on r1797, has he actually run the 0.41 Installer and restarted Boinc?

Claggy

1)
http://setiathome.berkeley.edu/show_host_detail.php?hostid=3299266
Not used 0.41 installer.

2)
http://setiathome.berkeley.edu/show_host_detail.php?hostid=3806561
Ran installer, modified app_info.xml before restart. (This hosts xml was posted previously on this thread).

3)
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6890116
Ran installer, modified app_info.xml before restart.

The reason for different setups is that I make changes to one host first and measure the output before applying verified changes on other hosts.

Claggy · June 14, 2013, 03:37:02 AM

Quote from: Caprio on June 14, 2013, 01:56:28 AM
2)
http://setiathome.berkeley.edu/show_host_detail.php?hostid=3806561
Ran installer, modified app_info.xml before restart. (This hosts xml was posted previously on this thread).

Your host now has got a couple of GPU AP v6 Wu's, it'll be the abundance of MB v7 Wu's that stopped it getting any earlier,
turning off MB v7 in your preferences will increase your allocation of GPU AP v6 Wu's. (Subject to you having enough free Wu slots out of your 100)

Claggy

Caprio · June 15, 2013, 05:19:55 AM

Indeed one host actually has some AP GPU.

But this has not.
http://setiathome.berkeley.edu/results.php?hostid=6890116&offset=0&show_names=0&state=0&appid=12

Maybe I did not select the GPU AP at install.

Is there an app available for using AVX for setiathome (without CUDA)?

Claggy · June 15, 2013, 05:28:28 AM

Quote from: Caprio on June 15, 2013, 05:19:55 AM
Is there an app available for using AVX for setiathome (without CUDA)?

What?

Claggy

Caprio · June 15, 2013, 06:19:50 AM

An app using the ivy bridge embedded GPU, either for astropulse or multibeam.

Claggy · June 15, 2013, 06:54:46 AM

Quote from: Caprio on June 15, 2013, 06:19:50 AM
An app using the ivy bridge embedded GPU, either for astropulse or multibeam.

Check out Number Crunching at Seti, there has been a Intel OpenCL Astropulse app in Beta testing for months,
and it was put on Seti Beta a couple of days ago to facilitate server bug hunting.

Claggy

Caprio · June 18, 2013, 06:07:26 AM

Now I have cache stacked up with a lot of ap tasks. Not many are cuda. Are there some way to tell the scheduler to put only or majority cuda ap tasks up my que? I saw for example that horacio had only AP GPU tasks up his que.

http://setiathome.berkeley.edu/hosts_user.php?userid=264505

Claggy · June 18, 2013, 07:19:01 AM

Quote from: Caprio on June 18, 2013, 06:07:26 AM
Now I have cache stacked up with a lot of ap tasks. Not many are cuda. Are there some way to tell the scheduler to put only or majority cuda ap tasks up my que? I saw for example that horacio had only AP GPU tasks up his que.

http://setiathome.berkeley.edu/hosts_user.php?userid=264505

?

MB v7 has CPU, Cuda and ATI OpenCL apps,

AP has CPU, Nvidia OpenCL and ATI OpenCL apps, there is no such thing as a Cuda AP app,

What are you trying to do? are you after Cuda MB v7 tasks, or are you after Nvidia OpenCL AP tasks?

You can bias the scheduler's choice by ticking only the type of work you want in your Setiathome preferences, then tick the 'If no work for selected applications is available, accept work from other applications?' box too.

Claggy

Caprio · June 18, 2013, 02:22:27 PM

Indeed, I meant Open CL AP tasks. Unchecking v7 will get you to prefer ap tasks, but how to tell the scheduler to prefer Open CL tasks before CPU tasks?

Claggy · June 18, 2013, 08:26:36 PM

Quote from: Caprio on June 18, 2013, 02:22:27 PM
Indeed, I meant Open CL AP tasks. Unchecking v7 will get you to prefer ap tasks, but how to tell the scheduler to prefer Open CL tasks before CPU tasks?

Once your GPU has done it's 10 validations for the 'AstroPulse v6 (anonymous platform, nvidia GPU)' planclass the scheduler will know which device/app_version is fastest, and that device will get work first,

Claggy

Caprio · June 22, 2013, 11:20:13 PM

Nice little detail. Was it documented somewhere, excepti in the seti/boinc source code?

How to configure v6 AP GPU tasks

Caprio

June 13, 2013, 05:57:38 AM

Claggy

June 13, 2013, 06:35:19 AM #1

arkayn

June 13, 2013, 06:42:59 AM #2

Claggy

June 13, 2013, 06:56:29 AM #3

William

June 13, 2013, 05:01:57 PM #4

Caprio

June 14, 2013, 01:56:28 AM #5

Claggy

June 14, 2013, 03:37:02 AM #6

Caprio

June 15, 2013, 05:19:55 AM #7

Claggy

June 15, 2013, 05:28:28 AM #8

Caprio

June 15, 2013, 06:19:50 AM #9

Claggy

June 15, 2013, 06:54:46 AM #10

Caprio

June 18, 2013, 06:07:26 AM #11

Claggy

June 18, 2013, 07:19:01 AM #12

Caprio

June 18, 2013, 02:22:27 PM #13

Claggy

June 18, 2013, 08:26:36 PM #14

Caprio

June 22, 2013, 11:20:13 PM #15