BOINC
Add option to not stop non-CPU intensive (NCI) tasks.
Describe the problem I have non-CPU intensive tasks alongside CPU intensive tasks. I use the snooze option quite regularly and it would be nice if the NCI tasks are won't stop.
Describe the solution you'd like I'd like an option inside the "Computing" preferences to not stop NCI tasks, even if BOINC is suspended.
I believe 'Manual snooze' means 'Snooze anything including NCI' and this is correct behavior. Maybe it will be better to add 'Snooze excluding NCI' option but with better caption?
Honestly, we can call it whatever you want, if it makes my life easier. :) What about a scenario, when the boinc snooze because an exclusive app is running?
This is significantly different scenario. And there is a similar ticket but for Android #1905 Core changes in client will be definitely similar.
If anybody feels minded to work this issue up into a full PR, please also add the final missing option "snooze/suspend CPUs, but leave GPUs running".
Yes, I'm aware of the formal statement that every GPU task requires CPU support, but let's be real-world about this. Anybody who's ever run a GPU app under BOINC knows that the actual CPU demand varies massively from project to project, from application to application, from programming language to programming language, from manufacturer to manufacturer. The person who knows most about the performance characteristics of the particular computer is the person sitting in front of the keyboard and screen - the user. Give them the choice.
Maybe it will be better to add 'Snooze excluding NCI' option but with better caption?
Remember that the task bar menu is the same in Simple View as in Advanced View. Simple View users don't understand non-CPU-intensive tasks; I think they would find 'Snooze excluding NCI' confusing.
please also add the final missing option "snooze/suspend CPUs, but leave GPUs running".
A better approach would be to leave the options as they are, but allow the user to uncheck (untick) Snooze GPU when Snooze is selected. Currently they can't do that because Snooze GPU is disabled when Snooze is checked. In other words, just don't disable Snooze GPU when Snooze is checked, and update any underlying logic.
"Usually" is not a good basis for denying a user choice. I have two tasks in front of me using 1.49% and 1.83% of a CPU alongside the GPU.