Hi,
Is there any news on the possibility of limiting the CPU usage of BOINC according to the CPU temperature.
I saw in these forums that this is a feature requested for a very long time.
A native implementation in the BOINC client of this feature would be highly appreciated.
Thanks!

---

if you go to the git-hub site and look at feature requests there you could see if anyone is down as working on it. It does sort of happen with lots of modern CPUs as they automagically throttle speed if they get too hot.

Edit:Worth looking at this feature request. Doesn't look like anyone is actively working on it at least at a quick glance.

I wonder if the impetus to develop a native BOINC solution is diminished by the popular TThrottle application that provides exactly what you request.

No reason to reinvent the wheel as it were . . . . .

https://efmer.com/download-tthrottle/

BoincTasks and TThrottle

---

Hi,

I had looked into this possibility, unfortunately TThrottle works only on Microsoft Wndows computer, not on GNU Linux.
I also tested boinctask, but it is not adapted and not able to support a park of more than 400 Linux workstations.

---

CPU temperature control should be down to the cooling solution. if you have to limit application execution/performance then there's something wrong with your cooling solution.

---

CPU temperature control should be down to the cooling solution. if you have to limit application execution/performance then there's something wrong with your cooling solution.

The cooling is good, the aim of the limitation is to limit the noise of the fans so as not to disturb the users near a station with boinc in operation in a public environment.

---

I run BoincTasks in Linux using the Wine emulator with great success. But I have never tried to run eFMer's TThrottle under WINE as I directly control my cooling solutions for both the cpus and gpus.

---

I also currenttly run one instance of BOINC on WINE and not had any success with Efmers tthrottle working.

I have tried several other Windows apps/programs with same result under WINE that cannot 'see' the temperature sensors.

My solution is to set the flag in
/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load to 1

this has the effect of stopping boinc jobs (that run at nice level 19) from throttling up the CPU (and so keeps the temp down, and the energy bill too!)

My solution is to set the flag in
/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load to 1

this has the effect of stopping boinc jobs (that run at nice level 19) from throttling up the CPU (and so keeps the temp down, and the energy bill too!)

Thank you,
it's a good idea and could have been useful to me, but apparently this possibility has unfortunately been removed from recent kernels.

---

... apparently this possibility has unfortunately been removed from recent kernels.

You may need to activate the 'ondemand' governor first.
The cpupower utility tells you which governors are available.

Example run on an intel i7:

cpupower frequency-info
analyzing CPU 0:
  driver: intel_cpufreq
  CPUs which run at the same hardware frequency: 0
  CPUs which need to have their frequency coordinated by software: 0
  maximum transition latency: 20.0 us
  hardware limits: 1.60 GHz - 3.90 GHz
  available cpufreq governors: ondemand performance schedutil
  current policy: frequency should be within 1.60 GHz and 3.90 GHz.
                  The governor "schedutil" may decide which speed to use
                  within this range.
  current CPU frequency: Unable to call hardware
  current CPU frequency: 3.70 GHz (asserted by call to kernel)
  boost state support:
    Supported: yes
    Active: yes
    3700 MHz max turbo 4 active cores
    3800 MHz max turbo 3 active cores
    3900 MHz max turbo 2 active cores
    3900 MHz max turbo 1 active cores

To activate 'ondemand' run

cpupower frequency-set -g ondemand

/sys/devices/system/cpu/cpufreq/ondemand/ignore_nice_load should then be available again.
On my AMD Threadripper systems it appears that 'ignore_nice_load' has no effect.
Instead, the CPU frequency change is controlled via XFR.