Although the idle priority in Windows for BOINC guarantees that it only executes when there's nothing else to execute, it's not so in Linux. Even at priority 39, BOINC still uses up about 5% of CPU.

Therefore, it would be desirable to make sure that when a system is under load, BOINC suspends execution and gets out of the way. User activity may work for interactive loads, but not for server-like loads.

Has it been considered to use the load averages on Linux and other Unixes to suspend execution at a user-configurable limit through the Web preferences?

---