Posted 12 May 2019 by
Azmodes
I've observed this behaviour since I modified all my machines to multithread long tasks. For the most part, things run as they should, but sometimes the client elects to run one or more tasks in addition to a long task that should already max out the CPU.
For example, an 8-core 9990k is running an 8-core long task (BOINC set to 100%, naturally) and every once in a while, one (or two or three etc.) non-long (1-core) task(s) is/are started and run alongside of it. This seems to be connected to the "Running high priority" task status, which apparently makes BOINC ignore multithreaded core numbers or something. Whether this has something to do with a task potentially missing a deadline is not really obvious to me, they usually have days and days left. My cache is also not that high, only 12 hours.
Any ideas?