Forum > GPU crunching

Modified SETI MB CUDA + opt AP package for full GPU utilization

<< < (49/58) > >>

sunu:

--- Quote from: The Grinch on 23 Jan 2009, 10:48:56 am ---I don't know if this will helps you

http://boinc.berkeley.edu/wiki/Anonymous_platform

--- End quote ---


Thanks, that was what I was looking for. Unfortunately I think I've already used

<avg_ncpus>3.0000</avg_ncpus>
<max_ncpus>3.0000</max_ncpus>

for AP with not the desired effect. Maybe I'll try again.

Raistmer:
use <ncpus>Ncores+1</ncpus> in cc_config.xml instead. IT works much better than fiddling with CPU shares.

sunu:
Raistmer here's the thing: I want to force 3+1 in a quad (not 4+1).

When I use <ncpus>4</ncpus> in cc_config.xml, boinc runs 4+1 when it is in normal mode and 3+1 in high priority mode.
When I use <ncpus>3</ncpus>, boinc runs 3+1 normal and 2+1 high priority.

All these are in boinc linux. Maybe it is a bug/feature?

Raistmer:
then try 2. If you don't care about idle cores it should work.  :P

Jason G:
Or you can try this: change the amount of cpus for the GPU app in the app_info file from 0.04, to 1  (or even 2  if needed)  then boinc can't allocate those cores to something else.  You might also want to check the flops setting in there is higher than for the CPU app (You can add #cpus (i.e. 1) and flops to CPU app section if it isn't there), so GPU app gets allocated first and hogs the required number of cores (x1)  prior to CPU apps being allocated(x remaining 3).

Jason

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version