I was wondering if the BOINC project has to be GPU enabled to use the GPU procesing. The reason I ask is because I participate in the "World Community Grid", and it would be nice to harness the power of the GPUs for that project.

Additionally, is it possible to run one BOINC project on the GPU and one on the CPU(s). If this is the case I might start generating maximum heat and put gpugrid.net on the GPU and WCG on the CPU.

Additionally, is it possible to run one BOINC project on the GPU and one on the CPU(s). If this is the case I might start generating maximum heat and put gpugrid.net on the GPU and WCG on the CPU.

To meet your target, you have to fool the boinc-client by announcing one additional CPU, e.g. Host 8166 with 5 CPU's.
On this host i am crunching 4 CPU-WU's (PrimeGrid) and one PS3-WU; the PrimeGrid-WU's with 99% per CPU and PS3 with about 5%.

???? How did you manage to do that??

Hi,
is the GPU application any slower doing this?

gdf

1. check out the sources.
2. file boinc/client/hostinfo_unix.C in line 764: p_ncpus = p_ncpus + 1; (+=1)
3. compile and use it (linux version)

for a windows version #2 should be done in ...hostinfo_win.C

1. check out the sources.

Hi gdf,

the only modification is: p_ncpus = p_ncpus + 1;

And this works (for me) very well...

There are other, more easier ways to let BOINC use more processors than the system actually has. Don't ask... Figure it out, its not difficult or far away!

I configured my C2D to use 3 cores and my Quad to use 5 and right now each crunches n+1 processes. So far this looks good, times seem not to drop.

My Quad with the 9800GT used to take 58600 seconds for one unit with 6.42. With 6.44 I can say that it takes somewhere in the range of 16-17 hours, but its a little difficult to say, as wall time for that unit can not be found under Linux. Time per step was 69.4ms.
Yesterday I switched to 5 tasks on that hosts and the unit that was just reported took no longer than 16,5 to max 17 hours at 70.754ms per step.

So it was a little slower, but not much. The 2% slowdown I'm willing to take, when I can have that core free.

On the C2D with 8800GTS the time per step increased from 52.8ms to 53.8ms.

In our forum other users (windows) have reported that this increases their crunching time for one unit a lot. So for Windows users forcing one extra core / thread is not expedient.
Might be some scheduler issue in the operating system, I don't know...

But for me and Stoffel it seems to run fine so far.
Lets monitor this for some days. I set my client to return results immediately, so that I can use the upload time as run time indicator. Maybe Linux is already ready for running the GPU thread in parrallel without (or just very small) impact to the run times... :)

He's talking about downloading the BOINC source files, editing a line and compiling it yourself. I don't want to be rude, but if you didn't get this it's probably not meant for you ;)

MrS

???? How did you manage to do that??

1. check out the sources.
2. file boinc/client/hostinfo_unix.C in line 764: p_ncpus = p_ncpus + 1; (+=1)
3. compile and use it (linux version)

for a windows version #2 should be done in ...hostinfo_win.C

???? How did you manage to do that??

1. check out the sources.
2. file boinc/client/hostinfo_unix.C in line 764: p_ncpus = p_ncpus + 1; (+=1)
3. compile and use it (linux version)

for a windows version #2 should be done in ...hostinfo_win.C

can be done both in linux and windows in cc_config.xml with attribute
<ncpus>

see here for documentaiton of cc_config
http://boinc.berkeley.edu/wiki/Client_configuration

But it slows down processing ALOT (maybe only on windows, problem with the scheduler?) 31k seconds before and 55k seconds after the modification.

We tracked down the issue (it was not the firewall causing the increase in computation time).

This <ncpus> is meant for diagnostics only and not meant to be used as a normal way to run boinc.

I would advise to wait for an official release.

things go bad when a project goes into "High Priority Mode" when you have it configured that way. And it doesn't stop BOINC from running 3 WUs from primgrid or any other project.