Posts by Sean Arrowsmith
|
1)
Message boards :
Number crunching :
Really low performance (I believe)
(Message 1907280)
Posted 15 Dec 2017 by  Sean Arrowsmith
Post: Thanks for the extra replies. I made a mistake, my memory is actually clocked at 2666. Whilst in the BIOS I also updated it, then applied the Asus OC Tuner to clock the CPU at 4Ghz (from 3.6Ghz), this has raised the temps by 10deg to 72deg C but with full load the 240mm water cooler is coping well and still 20deg cooler than the max 95deg the 1800x will tolorate, I also OC the Strix 1060 to 2075Mhz from the 1873Mhz I shall use you app_config and see how this goes. Thanks again all of you for your replies. |
|
2)
Message boards :
Number crunching :
Really low performance (I believe)
(Message 1907222)
Posted 15 Dec 2017 by Sean Arrowsmith
Post: Thanks David, I will look at this, but my app_info is large (standard one created by Lunatics), so not really sure which applications I need to create in the app_config file, so I will leave this alone as I do not know what I am doing and shall probably break it :-) Thanks |
|
3)
Message boards :
Number crunching :
Really low performance (I believe)
(Message 1907014)
Posted 14 Dec 2017 by Sean Arrowsmith
Post: Hi Zalster, I have put Milkyway down as a resource share of 0 to create this as the backup project whilst concentrating on SETI. Thanks, now hopefully I can get my Ryzen CPU optimized as Keith suggests. |
|
4)
Message boards :
Number crunching :
Really low performance (I believe)
(Message 1907002)
Posted 14 Dec 2017 by Sean Arrowsmith
Post: Thank you Keith for your advice. I have tried looking at other posts for info on what you are saying but confused, so if you could point me in the right direction I would be most grateful. SETI was the very first project I started on back in 2001 and then joined a couple of other projects mostly concentrating on Milkyway but I was to build SETI more. The other week when I started BOINC again you helped me get the right optimised apps. https://setiathome.berkeley.edu/forum_thread.php?id=82262 I have a Ryzen 1800x and as you know that has 8 cores (16 threads), how would I optimise the CPU as you suggested. My Ryzen is running at stock 3.690 freq and memory is at 2166Mhz |
|
5)
Message boards :
Number crunching :
Really low performance (I believe)
(Message 1906893)
Posted 14 Dec 2017 by Sean Arrowsmith
Post: Hi All, I am just a little concerned something is not right with my SETI crunching. Having got a new powerful PC I decided to start SETI crunching again, I was told where to get the optimized apps for my Ryzen 1800X/GTC 1060 STRYIX So my settings are 90% of processors with 90% of CPU time. I am running 2 projects (SETI and Milkyway) and they are spilt 50/50, since the 27th when I started , SETI is only doing 1256 (WorkDone) and Milkyway is averaging 32504 (WorkDone) Is this correct in your eyes. Is something drastic wrong? Why is Milkyway performing 10x better. Any ideas? Thanks |
|
6)
Message boards :
Number crunching :
Need help please with Optimized Lunatics Apps
(Message 1904058)
Posted 1 Dec 2017 by Sean Arrowsmith
Post: Thank you Grant and also Keith. I have made the changes but need to wait till the project comes back on line, so back onto crunching Milkyway |
|
7)
Message boards :
Number crunching :
Need help please with Optimized Lunatics Apps
(Message 1903214)
Posted 27 Nov 2017 by Sean Arrowsmith
Post: Thank you Keith, I have download the optimzed app Beta 6 and installed. I see that I need to add -sbs 192 -spike_fft_thresh 2048 -tune 1 64 1 4 to config my 1060. I presume I put this command line into the file ap_cmdline_win_x86_SSE2_OpenCL_NV.txt |
|
8)
Message boards :
Number crunching :
Need help please with Optimized Lunatics Apps
(Message 1903193)
Posted 27 Nov 2017 by Sean Arrowsmith
Post: Hi All, After a few years of not doing SETI as I used laptops, I have now brought a big PC and wish to start SETI again. Previoulsy I used to run Lunatics Optimized Apps for SETI and Astropulse, so after downloading BOINC and reattahcing to the SETI project, I then went off to get the Lunatics Apps. I have installed the apps for my Ryzen 7/GTX1060 STRIX PC, and restarted several times but I am still running the MB Win64 SSE3 stock apps. I have looked around and see no other install info so I do not know how to get BOINC to runs the optimized apps. Here is my app_info.xml <app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>AKv8c_r2549_winx86-64_SSE42xjfs.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-3-4_x64.dll</name>
<executable/>
</file_info>
<file_info>
<name>cmdline_AKv8c_r2549_winx86-64_SSE42xjfs.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_r2549_winx86-64_SSE42xjfs.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>cmdline_AKv8c_r2549_winx86-64_SSE42xjfs.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_r2549_winx86-64_SSE42xjfs.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>cmdline_AKv8c_r2549_winx86-64_SSE42xjfs.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_x64_AVX_CPU_r2692.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-3-4_x64.dll</name>
<executable/>
</file_info>
<file_info>
<name>ap_cmdline_win_x64_AVX_CPU.txt</name>
</file_info>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<plan_class>sse2</plan_class>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<plan_class>sse2</plan_class>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>703</version_num>
<platform>windows_x86_64</platform>
<plan_class>sse</plan_class>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>703</version_num>
<platform>windows_intelx86</platform>
<plan_class>sse</plan_class>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>701</version_num>
<platform>windows_x86_64</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>701</version_num>
<platform>windows_intelx86</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_cmdline.txt</open_name>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<cmdline></cmdline>
<file_ref>
<file_name>AP7_win_x64_AVX_CPU_r2692.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>ap_cmdline_win_x64_AVX_CPU.txt</file_name>
<open_name>ap_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>AstroPulse_Kernels_r2887.cl</name>
</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>710</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>705</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>705</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>705</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>705</version_num>
<platform>windows_x86_64</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</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>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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>opencl_nvidia_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_version>
<app_name>astropulse_v7</app_name>
<version_num>710</version_num>
<platform>windows_intelx86</platform>
<avg_ncpus>0.04</avg_ncpus>
<max_ncpus>0.2</max_ncpus>
<plan_class>cuda_opencl_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_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>opencl_nvidia_100</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_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>1</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>AstroPulse_Kernels_r2887.cl</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_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>opencl_nvidia_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_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_cc1</plan_class>
<cmdline></cmdline>
<coproc>
<type>CUDA</type>
<count>1</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>AstroPulse_Kernels_r2887.cl</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_x64_SSE3_VS2008_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_SSE3_VS2008.txt</name>
</file_info>
<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>
<file_ref>
<file_name>MB8_win_x64_SSE3_VS2008_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_SSE3_VS2008.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>
<file_ref>
<file_name>MB8_win_x64_SSE3_VS2008_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_SSE3_VS2008.txt</file_name>
<open_name>mb_cmdline.txt</open_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>Lunatics_x41zi_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.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>
<api_version>6.2.18</api_version>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app>
<name>setiathome_v8</name>
</app>
<file_info>
<name>Lunatics_x41zi_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>mbcuda.cfg</name>
</file_info>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<api_version>6.2.18</api_version>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<api_version>6.2.18</api_version>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<api_version>6.2.18</api_version>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<api_version>6.2.18</api_version>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v8</app_name>
<version_num>800</version_num>
<platform>windows_intelx86</platform>
<api_version>6.2.18</api_version>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_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>6.2.18</api_version>
<plan_class>cuda32</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_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>6.2.18</api_version>
<plan_class>cuda22</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_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>6.2.18</api_version>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_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>6.2.18</api_version>
<plan_class>cuda42</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_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>6.2.18</api_version>
<plan_class>cuda50</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41zi_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>mbcuda.cfg</file_name>
</file_ref>
</app_version>
</app_info> Here is my event log 27/11/2017 19:51:03 | | cc_config.xml not found - using defaults 27/11/2017 19:51:03 | | Starting BOINC client version 7.8.3 for windows_x86_64 27/11/2017 19:51:03 | | log flags: file_xfer, sched_ops, task 27/11/2017 19:51:03 | | Libraries: libcurl/7.47.1 OpenSSL/1.0.2g zlib/1.2.8 27/11/2017 19:51:03 | | Data directory: C:\ProgramData\BOINC 27/11/2017 19:51:03 | | Running under account Sean 27/11/2017 19:51:06 | | CUDA: NVIDIA GPU 0: GeForce GTX 1060 6GB (driver version 388.13, CUDA version 9.1, compute capability 6.1, 4096MB, 3562MB available, 4730 GFLOPS peak) 27/11/2017 19:51:06 | | OpenCL: NVIDIA GPU 0: GeForce GTX 1060 6GB (driver version 388.13, device version OpenCL 1.2 CUDA, 6144MB, 3562MB available, 4730 GFLOPS peak) 27/11/2017 19:51:06 | SETI@home | Found app_info.xml; using anonymous platform 27/11/2017 19:51:06 | | Host name: SeanRyzen 27/11/2017 19:51:06 | | Processor: 16 AuthenticAMD AMD Ryzen 7 1800X Eight-Core Processor [Family 23 Model 1 Stepping 1] 27/11/2017 19:51:06 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 htt pni ssse3 fma cx16 sse4_1 sse4_2 movebe popcnt aes f16c rdrandsyscall nx lm avx avx2 svm sse4a osvw skinit wdt tce topx page1gb rdtscp fsgsbase bmi1 smep 27/11/2017 19:51:06 | | OS: Microsoft Windows 10: Core x64 Edition, (10.00.16299.00) 27/11/2017 19:51:06 | | Memory: 15.93 GB physical, 18.30 GB virtual 27/11/2017 19:51:06 | | Disk: 232.43 GB total, 103.79 GB free 27/11/2017 19:51:06 | | Local time is UTC +0 hours 27/11/2017 19:51:06 | | VirtualBox version: 5.2.0 27/11/2017 19:51:06 | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 8393327; resource share 100 27/11/2017 19:51:06 | | General prefs: from http://bam.boincstats.com/ (last modified 17-Aug-2013 11:04:29) 27/11/2017 19:51:06 | | Host location: none 27/11/2017 19:51:06 | | General prefs: using your defaults 27/11/2017 19:51:06 | | Reading preferences override file 27/11/2017 19:51:06 | | Preferences: 27/11/2017 19:51:06 | | max memory usage when active: 9787.17 MB 27/11/2017 19:51:06 | | max memory usage when idle: 14680.75 MB 27/11/2017 19:51:06 | | max disk usage: 100.00 GB 27/11/2017 19:51:06 | | suspend work if non-BOINC CPU load exceeds 25% 27/11/2017 19:51:06 | | (to change preferences, visit a project web site or select Preferences in the Manager) 27/11/2017 19:51:17 | | Suspending computation - CPU is busy 27/11/2017 19:51:27 | | Resuming computation[/code][/quote] |
|
9)
Message boards :
Number crunching :
GPU usage oscillation
(Message 1404206)
Posted 17 Aug 2013 by Sean Arrowsmith
Post: Hello, I have been try to work out what is happening on one of my PC's http://setiathome.berkeley.edu/show_host_detail.php?hostid=7068185 The system is AMD X645 with 8Gb memory and GTX460 (1Gb) I have just wiped the HD and reinstalled Win7, followed by Nvidia drivers 320.49 I put BOINC V7.0.64 (64bit) on and reattached to BAM which downloaded downloaded SETI and Engima. I then installed Lunatics 0.41 64bit installer. Upon running MSI Afterburner I can see the GPU usage going up and down. ie the usage oscillation at 99% for 7 seconds then drops to 30% for one seconds and then back up to 99% and so on it goes up and down. None of my other Nvidia PC's do this, is there a reason or a setting for this oscillation The GTX460 only is set up to crunch SETI MB Cuda WU Thank you |
|
10)
Message boards :
Number crunching :
All my CUDA taks are Completed, validation inconclusive
(Message 1374394)
Posted 31 May 2013 by Sean Arrowsmith
Post: Thanks for the replies. I am running a Geforce 7100 motherboard display as my main display, 2nd display is the GT520. Current driver is 307 Updating drivers just wrecks both drivers sets only only left with a single display running 600x480 and no other options. (even when doing a clean install). Only way to get back to normal is to uninstall and install 307. Just tried 320.18 now and same thing happened again. So forget about drivers as I don't know why it won't take. There are no errors in event log or on screen. The install process runs and then the screens blank and then only the single display and the 600/480 resolution appera then nothing even if I leave if or over an hour. A reboot just bring up the same so I have to uninstall and reinstall 307. Anyway I leave it for a few days as for some reason it has picked up an astropulse V6 604 to process via opencl_nvidia_100 and has 100 hours to go to finish so I'll see what happens. Previously before SETI 7 upgrade yesterday I was running Milkyway cuda on the GT520 for the last few months with no problems so if SETI causes problems then I just do Milkyway on the GT520 |
|
11)
Message boards :
Number crunching :
All my CUDA taks are Completed, validation inconclusive
(Message 1374264)
Posted 31 May 2013 by Sean Arrowsmith
Post: Running on BOINC 7.0.64(x64) and running SETI@home V7 7.00 tasks. It appears all my CUDA taks are being shown as inconclusive http://setiathome.berkeley.edu/results.php?hostid=5893526&offset=0&show_names=0&state=3&appid=11 Does my old Nvidia GT520 work OK on SETI CUDA taks? BOINC see the GPU 30/05/2013 21:05:15 | | CUDA: NVIDIA GPU 0: GeForce GT 520 (driver version 307.83, CUDA version 5.0, compute capability 2.1, 1024MB, 968MB available, 134 GFLOPS peak) 30/05/2013 21:05:15 | | OpenCL: NVIDIA GPU 0: GeForce GT 520 (driver version 307.83, device version OpenCL 1.1 CUDA, 1024MB, 968MB available, 134 GFLOPS peak) SETI is downloading me cuda42 and cuda50 taks but these just run in approx 15 seconds then finish and upload, looking online they all show as "Completed, validation inconclusive" Do I need to do something or is this a few duff tasks. Thanks |
|
12)
Message boards :
Number crunching :
Has SETI reduced the awarded credit per WU
(Message 1159524)
Posted 6 Oct 2011 by Sean Arrowsmith
Post: Thanks for the responses. It just seems like every time I alter something to BOINC or add a project I find that there are issues somewhere effecting everything that I was trying to do :-( Anyway, it's the science that is important and I would love to find something in the data I crunch that helps the world understand something a little better. |
|
13)
Message boards :
Number crunching :
Has SETI reduced the awarded credit per WU
(Message 1159413)
Posted 6 Oct 2011 by Sean Arrowsmith
Post: Has SETI reduced the awarded credit per WU, I ask because I have noticed a 50% drop in my RAC over the last few months. For example on 2 on my PCs (GTX480 with AMD645 Quad core, new in April 2011 and loaded with BOINC and Lunatics Opti-apps), the RAC increased from 0 to arround 7500 by May and stayed there at approx 7500 until mid July when the RAC dropped to 2500 and has slowly crept up to 3700 as of today. The PC's still operated for the approx length of time as they did back in May (approx 12hrs each day) so I can not work out why the RAC has dropped so much. Using Lunatics 0.38 Opti-apps Is the drop in RAC SETI based or because of something I have misconfigured. Thanks |
|
14)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1096822)
Posted 13 Apr 2011 by Sean Arrowsmith
Post: Thanks, I did the change to app_info. I have left things running for a few days to see how it's all working out but I have noticed today that the GPU is erroring out with computation errors a lot though it appear some might have gone through . See here http://setiathome.berkeley.edu/results.php?hostid=5883516&offset=0&show_names=0&state=5&appid= Could some knowledgeable person have a look and see if all is ok or what the erros mean so I can fix. I have tried searching these forums for the error (-1073741819 (0xffffffffc0000005)) number but did not find anything. From what I can see is that nothing on the GPU has worked since 8th March. Thanks PS, my other identical PC with GTX460 arrived today and that has started so I should see how these 2 identical PC's work against each other. |
|
15)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094631)
Posted 8 Apr 2011 by Sean Arrowsmith
Post:
That's me being a dumb. Thanks
I am on anonymous as running lunatic 0.37 |
|
16)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094622)
Posted 8 Apr 2011 by Sean Arrowsmith
Post: [quote GPUZ will show you how hard the GPU is working. On my GTX460, i set the app_info value so that the video card runs 2 WUs at the same time, resulting in the GPU loading being around 96%.[/quote] OK, GPUZ shows an average of 65% loading over the course of an hours worth of SETI GPU crunching with an average temp of 68Deg c. What is the app_info for 2 WU at the same time please. Is there an actual page some where showing what tweaks can be made to app_info etc as I remember one to increase the number of days to show your graph stats over. Thanks |
|
17)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094621)
Posted 8 Apr 2011 by Sean Arrowsmith
Post:
Do you mean I would be better off running the x86 app instead of the x64 app on my x64 Win7 system? |
|
18)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094275)
Posted 7 Apr 2011 by Sean Arrowsmith
Post:
Sorry, I do not understand anything about FLOPS etc. Could you explain more please about FLOPS. Also, how do I know that the GTX460 isbeing maxed out or not as the cuda app is running but the GPU temp is constant at 68Deg C which suggests that it's not working to capacity. It this right? Thanks. Ps I have now got the CPU's to crunch, I changed the app_info.xml file to make sure the CPU were poiniting to the corrct application AK_v8b_win_x64_SSE3 as for some reason they were pointing to a different application that did not exist. |
|
19)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094142)
Posted 7 Apr 2011 by Sean Arrowsmith
Post: Yes, my PC is http://setiathome.berkeley.edu/show_host_detail.php?hostid=5883516 I can now see clearly that something is wrong with the CPU from your help. I used Lunitics latest 037 installer. Unchecked AP but selected AMD SSE3 and also the CUDA during the installer. Done this twice before origianlly posting in case I had done it incorrectly. At least I know that it just does not work one one WU at a time but should be one per CPU/GPU The app_info.xml is the one from the lunatic package,I'll check it all over again to see what is what. thanks |
|
20)
Message boards :
Number crunching :
help: New Quad core PC with GTX460
(Message 1094082)
Posted 6 Apr 2011 by Sean Arrowsmith
Post: Hi, just got a new PC, a 4Gb Quad Core AMD II x4 with a Nvidia GTX460 I down loaded BOINC, installed it, then attached to SETI, SETI download the core apps and stuff. When finished I then installed the latest Lunatics Unified Installer from his site selecing X64 plus the Cuda option Now on my other Quad core (No GPU) I see in task view 4 tasks each being worked on at the same time (Same with my dual core) but on the new PC only 1 tasks is running and it's just using the lunaticCuda app and in tasks view it show for the only running task 0.04CPU + 1 NVIDA GPU IS this correct or should the apps be running on 4 CPU's plus the GPU? Any help would be great. |
Next 20
©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.