Forum > GPU crunching
What to use to only do MB on GPU and AP on CPU
Helmchen:
I want to use the CPU for only AP, while my GPU should do MB tasks.
Is this possible? What files do i have to use, i can't find anything about it. Actually i use Raistmers V10 but i can't always babysit the PC so that it does what i want.
greetings
Holger
KarVi:
Its possible to set this up.
The best way, would be to edit the app_info.xml, so that it only contains refrences to MB (setiathome_enhanced) rev 608 (603 could work to) pointing to the GPU/CUDA executable, and AP (astropulse_v5) rev 503, pointing to the AP_v5 executable.
This would make your client only do AP on the CPU and MB on the GPU, provided off course theres any work available.
M_M:
I have Q9650 (quad-core) and GTX295 (2xGPU). WinXP 32bit. Most of the time, everything works OK, as expected.
However, I find Boinc still not to intelegent... Quite often lately, in cache there are dozens of setiathome_enhanced and astropulse_v5 tasks, and I find boinc crunching 6x astropulse (on 4 logical CPUs!!!), while GPUs being idle... Again, there are setiathome_enhanced tasks waiting to be running...
So I have manually to suspend appropriate numbers of AP units, and resume them later to get everything back in order!
KarVi:
M_M:
The only way to do this and be sure its handled correctly, is to get the latest BOINC developement versions (6.6.17 or 6.6.18). These can handle CPU and GPU tasks individually, and makes sure such things don't happen. There is no need to change numbers of CPU's and so on, since BOINC then handles the allocation to CPU's and GPU's.
Since they are developement versions, they have other problems, but they work well enough on my CUDA system.
Helmchen:
I think i got things sorted, but sadly couldn't actually test it as i don't get any MB WUs
BOINC 6.6.17 did the trick, while 6.6.18 did nothing but killing WUs
thank you
Navigation
[0] Message Index
[#] Next page
Go to full version