Misuse of "High priority" mode in BOINC 6.6.36

[Raistmer]

Situation: there are 4 einstein tasks on host + 24 MW tasks with near zero CPU consumption. Host has 4 CPUs available for BOINC. If avg(max)_cpu for MW setted to 0.01, all 4 einstein tasks go into "high priority" mode totally blocking MW execution. If avg(max)_cpu for MW setted to 0.001, all 4 einstein tasks go into "high priority" mode + some of MW tasks go into "high priority" mode. Please, note, _ALL_ tasks in queue can run simultaneously. There is no other tasks in queue and no tasks near deadline (for example, deadline for einstein tasks 1 August, today is 22 July, execution time of every einstein task is 7 hours on that host). That is, there is no need at all to use "high priority" mode in such situation.

[davea]

Please set <rr_simulation> and send message log.

It's not clear that there's a bug here. Please email to boinc_alpha rather than using trac.