Message boards :
Number crunching :
Question about creating app_config.xml
Message board moderation
Author | Message |
---|---|
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Alright. I've been slow to try all these modifications, but finally install v0.41 from Crunchers Anonymous. Ran it for a bit and was happy to see the CPU time for Astropulses decrease by 50%. But with the GPU's, I notice the times lengthen a bit while percentage of cpu decreased form .281 to .02 After a bit,I thought about trying to create app_config.xml like the ones I've see on here. I copied this one, hoping to get 2 astropulses on each GPU and increase the CPU to 0.2 <app_config> <app> <name>astropulse_v6</name> <max_concurrent>2</max_concurrent> <gpu_versions> <gpu_usage>.5</gpu_usage> <cpu_usage>.2</cpu_usage> </gpu_versions> </app> <app> <name>setiathome_v7</name> <max_concurrent>2</max_concurrent> <gpu_versions> <gpu_usage>.5</gpu_usage> <cpu_usage>.2</cpu_usage> </gpu_versions> </app_config> and saved it as the above mention file to same location as app_info.xml in the bonic folder. I went under the advance tab and had Bonic read the Config file. Following this one of my GPU dropped out. The other 2 didn't change the percentages of cpu and no new Astropulses were started on the 2 remaining GPUs. The astropulse that was on the 3rd GPU was waiting to start. I couldn't figure out what happen. Only thing I could think of was the 2 working GPU are GTX650 Ti Boost and the third is only a GTX 650 Ti. Not much of a difference but maybe enough to cause it not to load? After a bit, I decided to delete the file and restart the computer. Once I did that, everything went back to how it was before I added the app_config.xml Any ideas? this is after the restart below cc_config.xml not found - using defaults Starting BOINC client version 7.2.33 for windows_x86_64 log flags: file_xfer, sched_ops, task Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6 Data directory: C:\ProgramData\BOINC CUDA: NVIDIA GPU 0: GeForce GTX 650 Ti BOOST (driver version 332.21, CUDA version 6.0, compute capability 3.0, 2048MB, 1955MB available, 1586 GFLOPS peak) CUDA: NVIDIA GPU 1: GeForce GTX 650 Ti BOOST (driver version 332.21, CUDA version 6.0, compute capability 3.0, 2048MB, 1970MB available, 1586 GFLOPS peak) CUDA: NVIDIA GPU 2: GeForce GTX 650 Ti (driver version 332.21, CUDA version 6.0, compute capability 3.0, 2048MB, 1970MB available, 1425 GFLOPS peak) OpenCL: NVIDIA GPU 0: GeForce GTX 650 Ti BOOST (driver version 332.21, device version OpenCL 1.1 CUDA, 2048MB, 1955MB available, 1586 GFLOPS peak) OpenCL: NVIDIA GPU 1: GeForce GTX 650 Ti BOOST (driver version 332.21, device version OpenCL 1.1 CUDA, 2048MB, 1970MB available, 1586 GFLOPS peak) OpenCL: NVIDIA GPU 2: GeForce GTX 650 Ti (driver version 332.21, device version OpenCL 1.1 CUDA, 2048MB, 1970MB available, 1425 GFLOPS peak) SETI@home | Found app_info.xml; using anonymous platform Processor: 8 AuthenticAMD AMD FX(tm)-9370 Eight-Core Processor [Family 21 Model 2 Stepping 0] 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 popcnt aes syscall nx lm svm sse4a osvw ibs xop skinit wdt lwp fma4 tce tbm topx page1gb rdtscp OS: Microsoft Windows 7: Professional x64 Edition, Service Pack 1, (06.01.7601.00) Memory: 31.97 GB physical, 63.93 GB virtual Disk: 931.41 GB total, 847.00 GB free Local time is UTC -6 hours Einstein@Home | URL http://einstein.phys.uwm.edu/; Computer ID 10267709; resource share 100 SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 7135571; resource share 100 SETI@home | General prefs: from SETI@home (last modified 08-Dec-2013 19:43:06) SETI@home | Computer location: work | General prefs: using separate prefs for work | Reading preferences override file | Preferences: | max memory usage when active: 16366.31MB | max memory usage when idle: 29459.35MB | max disk usage: 838.27GB | max CPUs used: 5 | don't use GPU while active | suspend work if non-BOINC CPU load exceeds 25% | (to change preferences, visit a project web site or select Preferences in the Manager) | Not using a proxy |
spitfire_mk_2 Send message Joined: 14 Apr 00 Posts: 563 Credit: 27,306,885 RAC: 0 |
SETI@home | Found app_info.xml; using anonymous platform ^ You already got it. Modify it to run two of whatever you want. No need for more files cluttering stuff up. |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
well, I change every 0.04 to 0.3 and every 1 to 0.5 so now the GPUs are running cpu 0.3 + 0.5 GPU but now how do I get it to load a second astropulse onto each GPU? Opps looks like now it is only using 1 GPU fully and 1/2 of another, the third is not being used at all..Hmmm..suggestions? |
spitfire_mk_2 Send message Joined: 14 Apr 00 Posts: 563 Credit: 27,306,885 RAC: 0 |
Did you remove the app_config? |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
yes I deleted it before I changed anything and restarted the computer before changing the app_info.xml. Here's what the modified looks like <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.3</avg_ncpus> <max_ncpus>0.3</max_ncpus> <plan_class>cuda_opencl_100</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</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.3</avg_ncpus> <max_ncpus>0.3</max_ncpus> <plan_class>opencl_nvidia_100</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</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.3</avg_ncpus> <max_ncpus>0.3</max_ncpus> <plan_class>cuda_opencl_100</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</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.3</avg_ncpus> <max_ncpus>0.3</max_ncpus> <plan_class>opencl_nvidia_100</plan_class> <cmdline></cmdline> <coproc> <type>CUDA</type> <count>0.5</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_cuda42.exe</name> <executable/> </file_info> <file_info> <name>cudart32_42_9.dll</name> <executable/> </file_info> <file_info> <name>cufft32_42_9.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>cuda42</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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>cuda50</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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_cuda42.exe</name> <executable/> </file_info> <file_info> <name>cudart32_42_9.dll</name> <executable/> </file_info> <file_info> <name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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>609</version_num> <platform>windows_intelx86</platform> <plan_class>cuda23</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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>608</version_num> <platform>windows_intelx86</platform> <plan_class>cuda</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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>609</version_num> <platform>windows_x86_64</platform> <plan_class>cuda23</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.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>608</version_num> <platform>windows_x86_64</platform> <plan_class>cuda</plan_class> <avg_ncpus>0.30000</avg_ncpus> <max_ncpus>0.30000</max_ncpus> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> <file_ref> <file_name>Lunatics_x41zc_win32_cuda42.exe</file_name> <main_program/> </file_ref> <file_ref> <file_name>cudart32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>cufft32_42_9.dll</file_name> </file_ref> <file_ref> <file_name>mbcuda.cfg</file_name> </file_ref> </app_version> </app_info> |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
AstroPulses are not the same as CUDAs. To run 6 NV APs correctly you are going to need 6 Free Cores. Change the AP entries to; <avg_ncpus>0.04</avg_ncpus> <max_ncpus>1</max_ncpus> <plan_class>cuda_opencl_100</plan_class> <coproc> <type>CUDA</type> <count>0.5</count> </coproc> Then you will probably get your 6 APs to run. I would rather run 1 per card and use the cmdline settings to raise the usage myself... |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Thanks. I change it all the setting for 0.5 back to 1 so I could get the 1 Astropulse per card. I'll go back later and change the cudas back to 0.5 when I get some more free time so I can utilize the GPUs for the MBs and leave the astropulses alone. Was experimenting with the settings. Beginning to understand now, I appreciate your input and agree 1 AP per GPU. Thanks |
arkayn Send message Joined: 14 May 99 Posts: 4438 Credit: 55,006,323 RAC: 0 |
Thanks. I change it all the setting for 0.5 back to 1 so I could get the 1 Astropulse per card. I'll go back later and change the cudas back to 0.5 when I get some more free time so I can utilize the GPUs for the MBs and leave the astropulses alone. Was experimenting with the settings. Beginning to understand now, I appreciate your input and agree 1 AP per GPU. Thanks Also, remove the <Max_Concurrent> part of the app_config as that is only allowing you to run 2 total at a time. |
juan BFP Send message Joined: 16 Mar 07 Posts: 9786 Credit: 572,710,851 RAC: 3,799 |
..., the third is not being used at all..Hmmm..suggestions? By defoult Boinc uses only the most capable GPUs (theoricaly the fastest ones), thats could be the reason why it uses the first 2 GPUs and not the 3 one. cc_config.xml not found - using defaults You need to create a file named: cc_config .xml located on the Boinc Dada root (here for example: D:\Boinc) with: (becareful to avoid the .txt normaly added by notepath) <cc_config> <options> <use_all_gpus>1</use_all_gpus> </options> </cc_config> after that just go to the advanced option and read the configuraton files. If everyting was done well all your 3 GPU´s will start to crunch and the line must be changed to: 08/02/2014 18:45:20 | | Config: use all coprocessors |
Zalster Send message Joined: 27 May 99 Posts: 5517 Credit: 528,817,460 RAC: 242 |
Thanks I will try both of these when I get a chance. I've noticed that I've not gotten any new astropulses for the CPU since I installed v0.41 Last astropulse for the cpu was downloaded Feb. 05, 2014. I know I'm no where near my limit for cpu downloads, so did I mess up when I installed v0.41 in the section about astropulses? Thoughts? |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
I've noticed that I've not gotten any new astropulses for the CPU since I installed v0.41 Last astropulse for the cpu was downloaded Feb. 05, 2014. I know I'm no where near my limit for cpu downloads, so did I mess up when I installed v0.41 in the section about astropulses? Thoughts? You haven't screwed up, your old Stock 6.01 tasks are getting completed with the r1797 app, so your Lunatics installation is O.K, the scheduler will send work for the fastest device first, ie the GPU, it won't send work for the CPU until either Boinc does a CPU only request, or you reach the maximum of 100 GPU tasks, So either deselect 'Use Nivida GPU' in your project preferences for a while, and do some CPU only requests, Or increase you cache settings until you get 100 GPU tasks. Claggy |
©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.