Hi there, after using Arch for a couple of years I wanted to give Tumbleweed a try on a second partition on my laptop. After settin everything up I first noticed, that the device ran significantly hotter. A quick look into systemmonitor revealed, that CPU constantly jumps between 800MHz and 2.6GHz without any frequencies in between, even on idle. Contrary on Arch, the CPU frequencies adjust much more granular. I’ll attach a screenshot to show you what I mean.
On Arch, I haven’t set up anything regarding power management, so no tlp or anyhting.
The outputs of cpupower frequency-info are the same on both systems:
analyzing CPU 0:
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: Cannot determine or is not supported.
hardware limits: 800 MHz - 5.00 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 5.00 GHz.
The governor "powersave" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 800 MHz (asserted by call to kernel)
boost state support:
So now the question, what is openSuse doing differently and how can I get my CPU to run the same as on Arch?
These where both queried on battery. Interestingly, suse changes to balance_performance when AC is plugged in. The frequency behaviour does not change though.
Additional note, checking EPB values with x86_energy_perf_policy shows a value of 6 on both.
A possible explanation is that currently power-profiles-daemon conflicts with tlp, and tlp is probably being recommended for your laptop. So it changes when you plug in AC. No idea why frequency scaling behaves the same though. Have you done a stress test? Even arch doesn’t reach the high end of the frequency range.
Not stress tests per se, but you can see the CPU ramp up to higher clocks depending on the task.
What’s funny is, that on tumbleweed animations feel slightly mor sluggish, although clocks run higher, I assume constantly switching is hurting the performance here. On Arch, everything is buttery smooth, even when all clocks just above 800MHz
Any other ideas where someone could turn some knobs?