BOINC 6.4.5 and CUDA scheduling

[MarkJ]

Currently BOINC 6.4.5 requires a "feeder" task to run the coprocessor. On a quad core this means BOINC defaults to 3 cpu tasks + 1 gpu task. This can be overridden to use all 4 cores via the <ncpus> in cc_config so you get 4+1 tasks running.

The issue comes when it runs out of gpu tasks it tries to run 5 cpu tasks, resulting in having to share a cpu with multiple science apps. Alter the scheduler to run the "feeder" task without it taking an entire core (ie share with a science app) and when out of gpu work resort back to the 4 cpu cores. If its a coprocessor "feeder" task then don't count it as a cpu task.

[MarkJ]

BOINC 645 with CUDA task (4+1)

[MarkJ]

BOINC 645 with non-CUDA tasks (4+1)

[Nicolas]

The problem is that (last time I checked) the GPU app claims to use 90% CPU. Therefore, a project problem.

But I'm not sure how BOINC behaves if the app correctly claimed to use, say, 10%.

[davea]

Fixed in version 6.5

[Nicolas]

Changeset numbers or it didn't happen.

[MarkJ]

The Seti CUDA "feeder" app claims to use 0.04% CPU.

[Nicolas]

The ticket didn't ever mention SETI.

I was thinking about GPUGrid when I said it was claiming to use too much CPU.

[MarkJ]

I have attached to GPUGRID and their feeder app is claiming "0.04CPU's, 1 CUDA" (rightly or wrongly).

The screen shots show Seti & Einstein tasks running. I have since stopped doing Seti CUDA due to issues with their science app.

[romw]

Fixed in 6.6