Linux x64; boinc 7.4.23; AMD FX-4300 (4 core); Nvidia GTX-650; running projects Seti, Asteroids, & Einstein.

Looking at BoincManager -> Tasks -> (project) -> Properties and there is a value given for "Scheduling priority". For the past couple of months the values shown for the running projects have been fairly stable, Seti -1.10 / Einstein -1.30 / Asteroids -0.40 . With narrow range variations.

Resource shares are: Seti 85 / Einstein 10 / Asteroids 5.

Somewhere I've read about "long term debt" needing to be worked off and causing a project to consume more resource than otherwise might be expected. Asteroids runs one core 24/7 (max_concurrent=1) in spite of resource share 5; and Seti doesn't run any CPU (max_concurrent=3) in spite of resource share 85 and idle CPU cores.

Is priority -0.40 higher, i.e. more urgent, than -1.10 ? And, if so, why is Asteroids continuing for months at that priority? I have buffering set to 1 day plus 0.5 day. Presently Asteroids has 66 tasks buffered, with a total estimated time "remaining" of 130 hours. It is configured for CPU only.

Meanwhile, Seti could use 2 more cores but CPU work fetch is blocked since the CPU work queue is full (of Asteroids work).

Momentarily suspending Asteroids brings a flood of Seti CPU work but after resuming Asteroids, Seti works through its buffered tasks and fetches no more.
(Seti GPU work continues to flow normally and even Einstein GPU work takes a proportional slice of the GPU resource.)

So, what's the secret to getting Asteroids off of its priority limit? And how to "suggest" to boinc manager that 130 hours of Asteroids work exceeds the 1+0.5 day buffer parameters?

I can, of course, set NNT for Asteroids periodically but doesn't that then upset the long-term averaging boinc manager is trying to do?

Boinc 7.4.23 has the new "Event Log Diagnostic Flags" menu so just ask for a flag setting and it shall be done.