When 4 high priority tasks running it's impossible to run any additional tasks with small (0.01) CPU consumption. That is, all MW tasks are blocked from execution and GPU stays idle.
Is it possible to tell BOINC that it still able to run another tasks even if some project go into high priority mode?

---

Only by setting the amount of CPUs to X-1, as far as I know. Then the one CPU not doing work will do the GPU exclusively.

---

Only by setting the amount of CPUs to X-1, as far as I know. Then the one CPU not doing work will do the GPU exclusively.

Example:
4 high priority einstein tasks -> no MW tasks at all (avg(mx)_cpu==0.01)
4 high priority einstein tasks + MW avg(max_CPU)== 0.001 (showed as 0.00 by BOINC) -> enough MW tasks running.
So, problem solved but in rather strange way.

---

I was too optimistic.
Now, after BOINC 6.6.38 installation, all MW tasks are in "waiting to run" state, all 4 einstein tasks still running with high priority (there are no taks beside 4 einstein and less than 24 MW tasks on host still).
Some of MW tasks are aborted with message " -177 maximum elapsed time exceeded".
Probaly, it's countermeasure fighting with "waiting r run" state that prevents all MW task t continue.
GPU still idle.

---