Forum > GPU crunching
V10/11 of modified SETI MB CUDA + opt AP package for full multi-GPU+CPU use
Claggy:
--- Quote from: codeman05 on 08 Apr 2009, 09:08:14 am ---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 Claggy, I'll give this a shot tonight!
--- End quote ---
If you've been running the V10 team package, you already have it, you just need to re-use the .dll's and the 'MB_6.08_mod_CUDA_V10.exe' file,
or you could use the V11 app from this post: MB_6.08_mod_CUDA_V11_def_func_FFTW_ESTIMATE_update which has the same file name for easy upgrading!
Claggy
codeman05:
Hey guys,
I think I got everything finally running correctly...atleast initially.
Did a fresh reinstall of 6.6.20. Installed the V10 packages in post one of this thread, then copying in the V11 CUDA package. Using the stock app_info that came with the V10 pkg.
Now when I started up the project after all of this, I got 3 CUDA MB wu's and 8 AP units. My 3 GPU's knocked out the MB's in about 10 mins each. So great, CPU's and GPU's running 100%...greatness!
However once the MB units were finished, I was unable to get more.
I just have all 8 AP's running.
This is what I see in the BOINC log:
--- Quote ---4/8/2009 8:43:29 PM SETI@home [sched_op_debug] Starting scheduler request
4/8/2009 8:43:29 PM SETI@home Sending scheduler request: To fetch work.
4/8/2009 8:43:29 PM SETI@home Requesting new tasks
4/8/2009 8:43:29 PM SETI@home [sched_op_debug] CPU work request: 0.00 seconds; 0 idle CPUs
4/8/2009 8:43:29 PM SETI@home [sched_op_debug] CUDA work request: 864000.86 seconds; 3 idle GPUs
4/8/2009 8:43:34 PM SETI@home Scheduler request completed: got 0 new tasks
4/8/2009 8:43:34 PM SETI@home [sched_op_debug] Server version 607
4/8/2009 8:43:34 PM SETI@home Message from server: No work sent
4/8/2009 8:43:34 PM SETI@home Message from server: No work is available for Astropulse
4/8/2009 8:43:34 PM SETI@home Project requested delay of 11 seconds
4/8/2009 8:43:34 PM SETI@home [sched_op_debug] Deferring communication for 11 sec
4/8/2009 8:43:34 PM SETI@home [sched_op_debug] Reason: requested by project
4/8/2009 8:45:50 PM SETI@home [sched_op_debug] Starting scheduler request
4/8/2009 8:45:50 PM SETI@home Sending scheduler request: To fetch work.
4/8/2009 8:45:50 PM SETI@home Requesting new tasks
4/8/2009 8:45:50 PM SETI@home [sched_op_debug] CPU work request: 0.00 seconds; 0 idle CPUs
4/8/2009 8:45:50 PM SETI@home [sched_op_debug] CUDA work request: 864000.86 seconds; 3 idle GPUs
4/8/2009 8:45:55 PM SETI@home Scheduler request completed: got 0 new tasks
4/8/2009 8:45:55 PM SETI@home [sched_op_debug] Server version 607
4/8/2009 8:45:55 PM SETI@home Message from server: No work sent
4/8/2009 8:45:55 PM SETI@home Message from server: No work is available for Astropulse
--- End quote ---
Do I just need to give it more time, or could I have something off in the install?
AP wu's also look to be going at a 13hr-16 hour pace. I think it was about 40 hours before, so that's a nice improvment.
Raistmer:
non-teamed AK_v8b for AMD SSE3-level CPUs (for both x86 and x64 usage).
[attachment deleted by admin]
KarVi:
--- Quote from: Raistmer on 11 Apr 2009, 03:46:06 am ---non-teamed AK_v8b for AMD SSE3-level CPUs (for both x86 and x64 usage).
--- End quote ---
I have been trying to find info earlier in thread, but found nothing.
What are the advantages of this build?
From the name I gather its normal MB, not CUDA? Is it faster than previously released ak_v8b?
Raistmer:
--- Quote from: KarVi on 11 Apr 2009, 04:39:08 am ---
--- Quote from: Raistmer on 11 Apr 2009, 03:46:06 am ---non-teamed AK_v8b for AMD SSE3-level CPUs (for both x86 and x64 usage).
--- End quote ---
I have been trying to find info earlier in thread, but found nothing.
What are the advantages of this build?
From the name I gather its normal MB, not CUDA? Is it faster than previously released ak_v8b?
--- End quote ---
As I can remember there was no v8b for AMD available in non-teamed flavor. Only pre-release ones in closed section. This one should have same performance as pre-release (but it's fresh rebuild - small speed deviation in both sides possible). It can be used as "standalone" CPU MB opt app for AMD CPUs. Posted in this thread as replacement to "teamed" version for those who will do V10 "team" ->BOINC 6.6.20 transition.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version