Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
KarVi:
OK.
So if I'm allready running 6.6.20 with the official ak_v8b SSE3_AMD (which I believe is publicly available somewhere), there should be no difference?
I'll stick to that then :-)
Raistmer:
--- Quote from: KarVi on 11 Apr 2009, 05:37:24 am ---So if I'm allready running 6.6.20 with the official ak_v8b SSE3_AMD (which I believe is publicly available somewhere), there should be no difference?
--- End quote ---
Fine if available. There should be no difference in speed. Only CPUID features were changed recently.
n7rfa:
I seem to have a problem. I am running 6.6.20 and the v10 applications. I only see 2 tasks running in BOINC and when I check the Task Manager, I see 1 MB task running at 50%, 1 CUDA task running 0-1%, and 1 MB task with nothing loaded at 0%. (I am not running AP.)
What have I done wrong?
Thanks,
Here is my app_info.xml:
<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b_win_SSE3_GPU_CPU_team_V10.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft.dll</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-1-1a_upx.dll</name>
<executable/>
</file_info>
<file_info>
<name>MB_6.08_mod_CUDA_V10.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>607</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<file_ref>
<file_name>AK_v8b_win_SSE3_GPU_CPU_team_V10.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft.dll</file_name>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-1-1a_upx.dll</file_name>
</file_ref>
<file_ref>
<file_name>MB_6.08_mod_CUDA_V10.exe</file_name>
</file_ref>
</app_version>
</app_info>
Here is my local_prefs_override.xml:
<global_preferences>
<run_on_batteries>1</run_on_batteries>
<run_if_user_active>1</run_if_user_active>
<run_gpu_if_user_active>1</run_gpu_if_user_active>
<start_hour>0.000000</start_hour>
<end_hour>0.000000</end_hour>
<net_start_hour>0.000000</net_start_hour>
<net_end_hour>0.000000</net_end_hour>
<leave_apps_in_memory>0</leave_apps_in_memory>
<confirm_before_connecting>0</confirm_before_connecting>
<hangup_if_dialed>0</hangup_if_dialed>
<dont_verify_images>0</dont_verify_images>
<work_buf_min_days>0.100000</work_buf_min_days>
<work_buf_additional_days>0.500000</work_buf_additional_days>
<max_ncpus_pct>100.000000</max_ncpus_pct>
<cpu_scheduling_period_minutes>60.000000</cpu_scheduling_period_minutes>
<disk_interval>60.000000</disk_interval>
<disk_max_used_gb>100.000000</disk_max_used_gb>
<disk_max_used_pct>50.000000</disk_max_used_pct>
<disk_min_free_gb>0.100000</disk_min_free_gb>
<vm_max_used_pct>75.000000</vm_max_used_pct>
<ram_max_used_busy_pct>50.000000</ram_max_used_busy_pct>
<ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
<max_bytes_sec_up>0.000000</max_bytes_sec_up>
<max_bytes_sec_down>0.000000</max_bytes_sec_down>
<cpu_usage_limit>100.000000</cpu_usage_limit>
</global_preferences>
and here is my cc_config.xml:
<cc_config>
<log_flags>
<task>1</task>
<file_xfer>1</file_xfer>
<sched_ops>1</sched_ops>
<cpu_sched_debug>0</cpu_sched_debug>
<work_fetch_debug>0</work_fetch_debug>
</log_flags>
<options>
<save_stats_days>30</save_stats_days>
<report_results_immediately>1</report_results_immediately>
</options>
</cc_config>
cyclejon:
--- Quote from: n7rfa on 11 Apr 2009, 11:19:22 am ---I seem to have a problem. I am running 6.6.20 and the v10 applications. I only see 2 tasks running in BOINC and when I check the Task Manager, I see 1 MB task running at 50%, 1 CUDA task running 0-1%, and 1 MB task with nothing loaded at 0%. (I am not running AP.)
What have I done wrong?
--- End quote ---
Your app_info is from the team mod, it doesn't work with 6.6.* There are other posts in this thread about which files you need. As well as this thread on the seti forums http://setiathome.berkeley.edu/forum_thread.php?id=52589 for the correct app_info.
Raistmer:
--- Quote from: cyclejon on 11 Apr 2009, 12:18:04 pm ---
Your app_info is from the team mod, it doesn't work with 6.6.*
--- End quote ---
V10 pack does work with any 6.6.x BOINC including 6.6.20. Actually I running it exactly with BOINC 6.6.20 right now.
But starting from BOINC 6.6.14 as was mentioned many times in this thread already there is possibility to use BOINC own scheduling mechanism for CUDA applications to run both CPU and GPU SETI MB versions simultaneously. That's why team pack can be disabled now.
But to do this you need replace app_info.xml _and_ SETI CPU MB "teamed" app ("teamed" AK_v8). Only SETI CUDA MB and SETI AP should be leaved untouched while upgrading from V10 pack to BOINC 6.6.20.
You need to delete cc_config.xml also (or just edit it to remove ncpus section if you use cc_config for some other purposes too).
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version