Activity not working like it did before

[Sandman192]

Describe the bug

I activity where you select Run Always is to ignore what's in you performance settings is not working in v8.02 anymore.
I have in the setting to Use At most 75% of the CPUs when in in use but BOINC is using all CPU when in use.
Again v7.xx ignored what's in the compute performance and ran no matter what when set to Run Always.

Steps to reproduce

No response

Expected behavior

To Always Run CPU when set to Always Run and ignore Compute Performance.

Screenshots

System information

Win 11
BOINC 8.0.2

Additional context

No response

[davidpanderson]

I don't understand the above.
Please clarify what it does and what you think it should do.

[AenBleidd]

@davidpanderson, I have tried to read this ticket again, and it looks like I know what's it about.
Before - when there was only one set of settings (those that are now named 'Not In Use') - when checking in the BOINC Manager 'Run always', BOINC client was using all the available resources and was ignoring all the preferences set by the user.
However now, this setting is ignored when we are talking about the CPU usage.
Let's say, I have the next CPU settings (GPU looks fine according to my testing, not sure about the RAM):

• When 'In Use': use 80% of the CPUs (80% out of 20 is 16 in my case)
• When 'Not in Use': use 100% of the CPUs (20 in my case)
  And now when I switch between 'Run always' and 'Run based on preferences', nothing changes: always 'In Use' settings are used. So this switch does basically nothing (at least in the case with CPUs).
  So, either it needs to be fixed and when selected, BOINC client should ignore all the preferences, or the new menu behavior should be clarified and explained better to avoid misunderstanding.

[davidpanderson]

The meaning of "Run always" (it seems to me) is that the following are disabled:
"Suspend when computer is in use",
"Suspend when non-BOINC CPU usage is above X"
"Suspend when no mouse or keyboard input in last X minutes"
"Suspend when on battery"

The other preferences remain in effect -
it doesn't mean 'Run always and use 100% of everything".

Is this the actual behavior? If not I'll fix it.

[AenBleidd]

I think it works exactly as described by @davidpanderson but worth testing it more extensively.