Message boards :
Number crunching :
Issues configuring app_info.xml: "Your app_info.xml file doesn't have a usable version of SETI@home v8."
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 31 Oct 02 Posts: 9 Credit: 9,769,912 RAC: 0 ![]() |
I'm getting this error: 11/11/2018 22:29:05 | SETI@home | Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v8. Can't figure out what I have setup wrong in the app_info file. Contents is below. Any idea? <app_info> <app> <name>setiathome_v8</name> </app> <file_info> <name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-3-4_x86.dll</name> <executable/> </file_info> <file_info> <name>MultiBeam_Kernels_r3584.cl</name> </file_info> <file_info> <name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</name> </file_info> <app_version> <app_name>setiathome_v8</app_name> <version_num>819</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>820</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>812</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>812</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_sah</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_sah</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>819</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>820</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>812</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>812</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_sah</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_sah</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda50</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda42</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda32</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_intelx86</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda23</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda50</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda42</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda32</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <api_version>7.5.0</api_version> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>cuda23</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3584.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>MultiBeam_Kernels_r3584.cl</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> </app_info> |
Richard Haselgrove ![]() Send message Joined: 4 Jul 99 Posts: 14661 Credit: 200,643,578 RAC: 874 ![]() ![]() |
Have you supplied all the files you need? EVERY file you need must be present in the SETI directory (alongside the app_info.xml file itself). If even one file is missing, that'll break it, and BOINC will probably delete all the other files as well. |
![]() ![]() ![]() ![]() Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 ![]() ![]() |
THat message can be deceiving when one has as many errors as you do. When you return errors, the server says "you have an app problem" Do you break it, then fix it? I see a couple of newer tasks that look ok If you fixed it, the server will only give you a few to try ... if those fail it will block you for longer. |
![]() ![]() ![]() ![]() Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 ![]() ![]() |
WTF???? 12 minutes for a 2080 running x41zi under Linux ???? Something was SERIOUSLY wrong! Then it appears you aborted everything and went to Win 10? |
![]() ![]() ![]() Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 ![]() ![]() |
The posted app_info is for the SoG application. But all I see in his tasks are CUDA42 and CUDA50. Looks like the app_info is being ignored and he is running the stock apps the server is trying out on his host. I wonder if the CUDA50 app is so far divorced from the current CUDA code in the latest drivers that it is spinning its wheels much of the time. Seti@Home classic workunits:20,676 CPU time:74,226 hours ![]() ![]() A proud member of the OFA (Old Farts Association) |
Richard Haselgrove ![]() Send message Joined: 4 Jul 99 Posts: 14661 Credit: 200,643,578 RAC: 874 ![]() ![]() |
I wonder if the CUDA50 app is so far divorced from the current CUDA code in the latest drivers that it is spinning its wheels much of the time.It was re-worked and re-tested for the introduction of Green Bank data in SETI@home_v8. But like all CUDA applications since 2008, it suffers very badly from lag at VLAR. It will be producing accurate results, but very inefficiently. |
Bruce Send message Joined: 15 Mar 02 Posts: 123 Credit: 124,955,234 RAC: 11 ![]() |
Hi Guys, This is the app_info.xml that I'm using for my RTX cards. <app_info> <app> <name>setiathome_v8</name> </app> <file_info> <name>MB8_win_x64_AVX_VS2010_r3330.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-3-4_x64.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline_win_x64_AVX_VS2010.txt</name> </file_info> <app_version> <app_name>setiathome_v8</app_name> <version_num>800</version_num> <platform>windows_x86_64</platform> <file_ref> <file_name>MB8_win_x64_AVX_VS2010_r3330.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x64.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x64_AVX_VS2010.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> <app> <name>astropulse_v7</name> </app> <file_info> <name>AP7_win_x86_SSE2_OpenCL_NV_r2887.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-3-4_x86.dll</name> <executable/> </file_info> <file_info> <name>ap_cmdline_win_x86_SSE2_OpenCL_NV.txt</name> </file_info> <app_version> <app_name>astropulse_v7</app_name> <version_num>705</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>.5</count> </coproc> <file_ref> <file_name>AP7_win_x86_SSE2_OpenCL_NV_r2887.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.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> </app_version> <app> <name>setiathome_v8</name> </app> <file_info> <name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3557.exe</name> <executable/> </file_info> <file_info> <name>libfftw3f-3-3-4_x86.dll</name> <executable/> </file_info> <file_info> <name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</name> </file_info> <app_version> <app_name>setiathome_v8</app_name> <version_num>819</version_num> <platform>windows_intelx86</platform> <avg_ncpus>0.04</avg_ncpus> <max_ncpus>0.2</max_ncpus> <plan_class>opencl_nvidia_SoG</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>.5</count> </coproc> <file_ref> <file_name>MB8_win_x86_SSE3_OpenCL_NV_SoG_r3557.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>libfftw3f-3-3-4_x86.dll</file_name> </file_ref> <file_ref> <file_name>mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt</file_name> <open_name>mb_cmdline.txt</open_name> </file_ref> </app_version> </app_info> The old cuda apps are slow, so is the SoG_r3584. For the RTX2080 you should use the SoG_r3557 app. It runs much quicker. Bruce |
![]() Send message Joined: 31 Oct 02 Posts: 9 Credit: 9,769,912 RAC: 0 ![]() |
Hi guys, Looks like it was just too many retries in a short period of time after I aborted a load of tasks while configuring the optimised apps. It worked as soon as I turned on my computer when I got home. As Bruce suggested I've downgraded to SoG_r3557. Looks like it's averaging about 6.5 minutes for each task, with two running in parallel so effectively 3.25 minutes. Is this about what would be expected with a 2080? It seems like the tasks chew tons of CPU, is that normal? Getting some interface lag just with it running in the background. |
![]() ![]() ![]() Send message Joined: 17 Feb 01 Posts: 34308 Credit: 79,922,639 RAC: 80 ![]() ![]() |
Just add this line .... -sbs 2048 -period_iterations_num 20 -high_perf -spike_fft_thresh 2048 -tune 1 64 1 4 -oclfft_tune_gr 256 -oclfft_tune_lr 16 -oclfft_tune_wg 256 -oclfft_tune_ls 512 -oclfft_tune_bn 64 -oclfft_tune_cw 64 to your mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt file. It is located in your projects folder. Save as txt and on the next task it will use the optimized params. With each crime and every kindness we birth our future. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13797 Credit: 208,696,464 RAC: 304 ![]() ![]() |
It seems like the tasks chew tons of CPU, is that normal? For OpenCL on Nvidia, yes. Grant Darwin NT |
Bruce Send message Joined: 15 Mar 02 Posts: 123 Credit: 124,955,234 RAC: 11 ![]() |
Hi Tilmitt, Glad to see that you got it working. Looks like it's averaging about 6.5 minutes for each task, with two running in parallel so effectively 3.25 minutes. Is this about what would be expected with a 2080?Looks like it is running a little slower than mine. At two at a time my run times are about 4min30sec. Performance can be increased by using the proper tune. It seems like the tasks chew tons of CPU, is that normal?Yes, this is normal. The newer Seti apps will slam the CPU pretty hard. This can be partially mitigated by using the -use_sleep parameter in your tune, but it will slow things down a bit, but might allow you to keep running two at a time. Getting some interface lag just with it running in the backgroundI have not noticed any lag on mine. You've only got 4 cores, are you running anything that is CPU intensive, besides the Seti GPU apps? Might have to cut back to one at a time. When your ready to try tuning, let me know. Edit - I see others have popped in while I was composing my reply Bruce |
![]() Send message Joined: 31 Oct 02 Posts: 9 Credit: 9,769,912 RAC: 0 ![]() |
Thanks guys. Gonna leave this on tonight and see how much it grinds out. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.