Found a nice tool showing that it is running at much to high clock speed for doing nothing. With energy savings activated in the GNOME settings.
cpupower frequency-info
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: Cannot determine or is not supported.
hardware limits: 2.20 GHz - 4.95 GHz
available frequency steps: 3.70 GHz, 2.80 GHz, 2.20 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 2.20 GHz and 3.70 GHz. The governor "schedutil" may decide which speed to use within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.06 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no
Found a nice tool showing that it is running at much to high clock speed for doing nothing. With energy savings activated in the GNOME settings.
cpupower frequency-info
The governor "schedutil" may decide which speed to use
within this range.
analyzing CPU 2:
driver: acpi-cpufreq
CPUs which run at the same hardware frequency: 2
CPUs which need to have their frequency coordinated by software: 2
maximum transition latency: Cannot determine or is not supported.
hardware limits: 2.20 GHz - 4.95 GHz
available frequency steps: 3.70 GHz, 2.80 GHz, 2.20 GHz
available cpufreq governors: conservative ondemand userspace powersave performance schedutil
current policy: frequency should be within 2.20 GHz and 3.70 GHz.
current CPU frequency: Unable to call hardware
current CPU frequency: 4.06 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: no