I have BOINC 7.16 on two PCs, set to start when inactive three minutes. I manage/check both in their GUI managers on my PC.

One Kubuntu GNU/Linux PC (BOINC 7.16.6+dfsg-1) is set to to compute when idle unless CPU system resource is over 93.75%. Hours after the users went to bed (and I closed all X/KDE programs) total CPU system resources usage (checked with htop) is 50% for other computation I run, but idling around 1% (or less) for OS & X, but BOINC won't start computing (saying 'busy' when it wasn't the case for hours.)

One Slackware GNU/Linux PC (mine, BOINC boinc-7.16.4-x86_64-1_SBo) is set to compute when idle unless CPU system resources usage is over 25%, and CPU system resources usage is typically 50+% for other computation I run, but BOINC started computing and won't stop.

What do I need to check/update so BOINC obeys start & continue & stop percentages for CPU resources? (instead of doing the exact opposite?)

I have BOINC 7.16 on two PCs, set to start when inactive three minutes. I manage/check both in their GUI managers on my PC.

One Kubuntu GNU/Linux PC (BOINC 7.16.6+dfsg-1) is set to to compute when idle unless CPU system resource is over 93.75%. Hours after the users went to bed (and I closed all X/KDE programs) total CPU system resources usage (checked with htop) is 50% for other computation I run, but idling around 1% (or less) for OS & X, but BOINC won't start computing (saying 'busy' when it wasn't the case for hours.)

One Slackware GNU/Linux PC (mine, BOINC boinc-7.16.4-x86_64-1_SBo) is set to compute when idle unless CPU system resources usage is over 25%, and CPU system resources usage is typically 50+% for other computation I run, but BOINC started computing and won't stop.

What do I need to check/update so BOINC obeys start & continue & stop percentages for CPU resources? (instead of doing the exact opposite?)

If you have suspend when cpu usage > x then why have suspend when computer in use as well?

Boinc is set to very low priority, any other job will run in preference. Try setting suspend when computer in use to no and see if that solves your problem.

Interesting.

Thinking the OP must be doing something strange, checked out my own system which normally runs with no restriction on BOINC's usage of resources I tried setting it to suspend when cpu usage is above 20,10, 5 and 1%. In all cases it continued to use about 95% of a core per task. I.E. No change from when no restriction on computing at all. I have yet to see if restarting BOINC makes any difference but as that occasionally trashes CPDN tasks am waiting to try that one out.

Edit BOINC 7.17 running on xubuntu20.04

Interesting.

Thinking the OP must be doing something strange, checked out my own system which normally runs with no restriction on BOINC's usage of resources I tried setting it to suspend when cpu usage is above 20,10, 5 and 1%. In all cases it continued to use about 95% of a core per task. I.E. No change from when no restriction on computing at all. I have yet to see if restarting BOINC makes any difference but as that occasionally trashes CPDN tasks am waiting to try that one out.

Edit BOINC 7.17 running on xubuntu20.04

The restriction is t’other way about, suspend when non-Boinc usage is above x% so if, for example, you’re watching a video and that is using a lot of cpu then it would stop all Boinc processing.

The restriction is t’other way about, suspend when non-Boinc usage is above x% so if, for example, you’re watching a video and that is using a lot of cpu then it would stop all Boinc processing.

In the example I gave where x=1 and non BOINC usage was over 20% it kept crunching using 95% of a core.

[...] Try setting suspend when computer in use to no and see if that solves your problem.

Not an option; I only need most (of 32) threads when compiling largest things (as a computer scientist, or doing other multi-core computation that's only part of the time) so most the rest of the time I want BOINC using many/most cores.

[...] Try setting suspend when computer in use to no and see if that solves your problem.

Not an option; I only need most (of 32) threads when compiling largest things (as a computer scientist, or doing other multi-core computation that's only part of the time) so most the rest of the time I want BOINC using many/most cores.

The suspend when cpu > x% should take care of that.

Temporarily trying suspend when computer in use = no would do no harm?