Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
sunu:
--- Quote from: codeman05 on 07 Apr 2009, 11:21:44 pm ---I did resets the project to see if that would make a difference...I now have 11 WU's running at once rather than 8.
--- End quote ---
You're ok, that's how it should be, 8 CPU + 3 GPU.
codeman05:
--- Quote from: sunu on 07 Apr 2009, 11:53:51 pm ---
--- Quote from: codeman05 on 07 Apr 2009, 11:21:44 pm ---I did resets the project to see if that would make a difference...I now have 11 WU's running at once rather than 8.
--- End quote ---
You're ok, that's how it should be, 8 CPU + 3 GPU.
--- End quote ---
Thanks Sunu.
BOINC just started telling me that there aren't any AP wu's available, so I guess thats why I'm only getting MBs right now.
The MB's are flying though. About 7 mins RT for each GPU's and ~22min for each CPU core.
sunu:
--- Quote from: codeman05 on 08 Apr 2009, 12:01:23 am ---BOINC just started telling me that there aren't any AP wu's available, so I guess thats why I'm only getting MBs right now.
The MB's are flying though. About 7 mins RT for each GPU's and ~22min for each CPU core.
--- End quote ---
Happy crunching then. Watch boinc to see when you get AP workunits.
Claggy:
--- Quote from: codeman05 on 07 Apr 2009, 11:21:44 pm ---Hi Sunu,
Thanks for the help.
I am running 6.6.20, sorry left that out before.
Sounds good, I was thinking it was something to get with the angle, but since it happened at the exact same time I switched over. I wasn't sure.
I did resets the project to see if that would make a difference...I now have 11 WU's running at once rather than 8.
here is my AP info
--- Code: ---- <app_info>
- <app>
<name>astropulse</name>
</app>
- <file_info>
<name>ap_5.00r103_SSE3.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>astropulse</app_name>
<version_num>500</version_num>
- <file_ref>
<file_name>ap_5.00r103_SSE3.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app>
<name>astropulse_v5</name>
</app>
- <file_info>
<name>ap_5.03r112_SSE3.exe</name>
<executable />
</file_info>
- <app_version>
<app_name>astropulse_v5</app_name>
<version_num>503</version_num>
- <file_ref>
<file_name>ap_5.03r112_SSE3.exe</file_name>
<main_program />
</file_ref>
</app_version>
- <app>
<name>setiathome_enhanced</name>
</app>
- <file_info>
<name>AK_v8b_win_x64_SSSE3x_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_x64_SSSE3x_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_x64_SSSE3x_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_x64_SSSE3x_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_x64_SSSE3x_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>
--- End code ---
--- End quote ---
A couple of things:
1: Boinc 6.6.x no longer needs the <ncpus> workaround, that was just for Boinc 6.4.x, Boinc 6.6.x now knows about the GPU's fitted, and so doesn't need this entry.
2: Your app_info has been opened and saved in Internet Explorer, you should only use notepad to edit it, it now has an extra space (known as Claggy's Space)
every time there is a <main_program /> or <executable /> entry, should be <main_program/> and <executable/>, also has lots of - entries that shouldn't be there.
3: The Team mode was get round problems with Boinc 6.4.x, you should now use V10 app stand alone, i.e. without the team part, and use a normal AK_V8 app for the CPU,
See this thread for a Proper app_info for Boinc 6.6.x: app_info for AP500, AP503, MB603 and MB608
Claggy
codeman05:
So basically to sum up, delete the CC_Config file since I no longer need the ncpu's flag. Install the V10 stand-alone app, and create a new app_info file using the link you provided.
In regards to the third item on your list, where can I find the V10 stand-alone app? Did a search but did not get any results back.
Thanks for the help Claggy, I'll give this a shot tonight!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version