UNIX/GNU/Linux Servers running BOINC clients (both command-line and GUI ) stop responding, so I regularly have to reboot command (if just GUI client) or hard reboot (sometimes server shells stop responding) which I see has been a common problem across OS. Do I need to set to stop number-crunching after CPU activity goes above a small amount, and if so, what? Some servers don't do anything else, and some also use GUI client or are also used as PCs (but usually not doing much else) so maybe percentages differ? Can you please suggest percentages to use on computers not only used for number-crunching, such as also 10+ BOINC GUI clients, or PCs that may also do graphics card number-crunching (other than BOINC) or a few things like system/root mail or other common daemons? This should even be standard part of GUI client setup because on a computer using that, clearly it's not just number-crunching and the person running that needs to have it responsive when using some small amount of CPU resources!

Rather than suspend computing above a certain CPU utilisation, I restrict the number of cores in use. For me keeping to N-1 where N is the number of real cores as opposed to including virtual cores allows my machines to always remain responsive. In summer when I don't use my main machine as a heater I go two or three cores less. I know that this may not get as much crunching done as only restricting things when non-BOINC work is above a certain percentage but it works for me.

Actually, it would be quite nice to have an option to cut the number of cores crunching in response to workload rather than suspend it.

In reply to Dave's message of 13 Mar 2025:

Rather than suspend computing above a certain CPU utilisation, I restrict the number of cores in use. For me keeping to N-1

I set one server (i.e., not running GUI client) to 8/32 cores but shell still stopped responding...

Actually, it would be quite nice to have an option to cut the number of cores crunching in response to workload rather than suspend it.

That option may exist somewhere further in configuration options.

It could be done via boinccmd and a shell script. It isn't something you can set up via config files or the gui. I could go to git-hub and put in a feature request but I doubt it would be a priority.