Forum > Windows

Please, help to balance CPU MB + ATI GPU MW on host under BOINC 6.6.36

(1/9) > >>

Raistmer:
Typical situation:
BOINC runs 4 SETI tasks w/o any MW tasks.
ATI GPU stays idle.
Another situation:
BOINC runs more than 10 MW tasks (from them only 3 actually do progress thanks to well-designed opt app by Gipsel, so it's not so bad), but only 3 SETI tasks. That is, one core stays idle (MW tasks consume almost no CPU, less tank CUDA MB).

Please, help to set project shares and other options to balance load.
Ideally I wanna see 4 SETI tasks + 3 or more (actuall no matter how more) MW tasks running simultaneously.
Maybe avg and max CPU in app_info should be changed too?

ADDON: additional info:
current project shares (only 2 projects active):
SETI - 10000
MW -  15000

IMHO bigger MW share should stimulate BOINC to run MW tasks.
But what I observe:
2 MW tasks started then were put in waiting for run state.
Short debt for MW (observing it via BOINCView) ~5000 s now and continues to increase.
Debt for SETI ~  -5000 s correspondingly....
Why BOINC doesn't allow MW tasks to run in this conditions?

Raistmer:
Even more info:
I suspended SETI for 1-2 seconds then resumed it.
BOINC started lot of MW tasks >10 then, after SETI resuming it starts 3 SETI tasks.
After few MW tasts completed it started 4th SETI task.
Short debts were resetted to zero. Now MW short debt increasing again and number of running MW tasks decreasing (that is BOINC refuses to start additional MW tasks when some of them completed).
What is wrong???
ADDON:
current app_info for MW:

    <flops>1.0e11</flops>
    <avg_ncpus>0.05</avg_ncpus>
    <max_ncpus>0.2</max_ncpus>
    <cmdline></cmdline>

Richard Haselgrove:
How are these MW tasks supposed to work?

I know they do the actual work on a GPU that BOINC knows nothing about. So they must be scheduled as CPU tasks, right? How do you get seven tasks, all believed by BOINC to be CPU tasks, to run at the same time? Non-computationally-intensive? 175% CPU utilisation?

What (and this is a serious question) does <cpu_sched_debug> put out?

Raistmer:
yes, MW use avg_cpu setting in app_info to claim it almost no use of CPU. That allows BOINC to run multiple instances of MW + some more CPU intensive tasks like SETI.
MW taks are processed completely on GPU indeed.
Will enable option you mentioned.

Jason G:
Right,  Ascribe a plan class with avg & max cpus of ~0.95 to SaH CPU tasks (AKv8 I presume). .... Initially should get 5 then drop back  :o

Navigation

[0] Message Index

[#] Next page