>>105671896
analyzing CPU 1:
driver: intel_pstate
CPUs which run at the same hardware frequency: 1
CPUs which need to have their frequency coordinated by software: 1
energy performance preference: performance
hardware limits: 800 MHz - 3.10 GHz
available cpufreq governors: performance powersave
current policy: frequency should be within 800 MHz and 3.10 GHz.
The governor "performance" may decide which speed to use
within this range.
current CPU frequency: 3.07 GHz (asserted by call to kernel)
boost state support:
Supported: yes
Active: yes
That did change something, now I can actually reach 3.1 Ghz and encoding av1 improved from 8 fps to 18 fps.
Why didn't cpupower freqency-set worked then?
And do I only have these
> available cpufreq governors: performance powersave
My other machine have (conservative ondemand userspace powersave performance schedutil)
Also is this
>echo performance | tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
permenante?
>>105671982
It does scale up and down, just not the full 3.1
I'm intrested because it did make a difference with encoding.
>>105672010
No, It's not thermal throttling, even with cpu stressing I couldn't reach 3.1 gHz.
But now after applying this >>105671896 I can reach 3.1 gHz.
So it was something on my end.
Heck even the GPU accelerated tasks perform better now.