Forum > Linux
SETI MB CUDA for Linux
Raistmer:
--- Quote from: sunu on 28 Jan 2009, 07:09:03 pm ---
--- Quote from: koschi on 28 Jan 2009, 07:02:15 pm ---The CUDA Linux app on my Q6600 with 9800GT (512MB) is also consuming 100% (so one full core) CPU time :-/
--- End quote ---
Yes, for performance reasons (both cuda app itself and general desktop responsiveness), Crunch3r made it that way .
--- End quote ---
Just wonder how to force CUDA MB to use 100% of CPU ?? ::) ::) ::)
REally more likely it's CPU fallback mode...
sunu:
--- Quote from: Raistmer on 28 Jan 2009, 08:39:16 pm ---
--- Quote from: sunu on 28 Jan 2009, 07:09:03 pm ---
--- Quote from: koschi on 28 Jan 2009, 07:02:15 pm ---The CUDA Linux app on my Q6600 with 9800GT (512MB) is also consuming 100% (so one full core) CPU time :-/
--- End quote ---
Yes, for performance reasons (both cuda app itself and general desktop responsiveness), Crunch3r made it that way .
--- End quote ---
Just wonder how to force CUDA MB to use 100% of CPU ?? ::) ::) ::)
REally more likely it's CPU fallback mode...
--- End quote ---
Raistmer look at the pre-release section, thread about linux cuda, second page, last post (from Crunch3r) (don't think I should post a direct link here ;) )
koschi:
If its fallback mode, then the CUDA app has CPU code that is 2-3 times faster than AK V8... ;D
Check my results, WUs with angle range of ~0.43 take just ~19 minutes, those took close to 1h before on my machine...
VLARs I'm killing with a cron script ::)
Raistmer:
Ok, I see.
--- Quote from: koschi on 28 Jan 2009, 09:26:45 pm ---Check my results, WUs with angle range of ~0.43 take just ~19 minutes, those took close to 1h before on my machine...
--- End quote ---
In task results I can see only CPU time, not wallclock time. 19min is big CPU time indeed for CUDA MB. It's interesting to know wallclock times for this build. Does additional usage of CPU lead to significant shrinkage wall clock time ?
Could anyone run PG*.wu test set with this build ?
sunu:
Raistmer, this is what Crunch3r said:
P.S. yes, the app needs a full core, cuz i've removed that part of the code that messes around with that on windows.
It also slows down the gpu if you'd run a 4+1 config.
Since it uses a full core, cpu time is actually wall time. It's not like in windows where cpu time << wall time.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version