I've just come to the violently embarassing realization that my CPU governor has been running on "powersave" for the last two and a half years cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governorSince realizing this and fixing it, all my Wayland issues with input latency and high CPU events causing the system to stutter have disappeared. I take back all the shit-talking in X11/Wayland threads, I finally get it now.
cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
You're welcome.#!/bin/shcpupower frequency-set -gperformance allx86_energy_perf_policy --all performance
#!/bin/shcpupower frequency-set -gperformance allx86_energy_perf_policy --all performance
Many years ago when I first built my own pc for the first time, after spending a small fortune I spent a week crying to myself for wasting money on a pc because my old Xbox performed better. I had plugged my monitor into the motherboard, not the gpu. We're all retarded at some point in our lives.
>>108026243>my CPU governor has been running on "powersavedid you blindly paste some shitass command in the terminal from an anon who said>try this and your Linux will get the same battery life as Windows
>>108026243kekMATE has a GUI applet for this, I just switch my governor using that
>>108026243dont feel badthink of all the money you saved on power
>>108026290Nah, I've never touched anything around it, I've never had an issue with battery life. If it isn't the default for intel_pstate on a laptop, I have no idea why it was on powersave. Shit's flying now though.
>>108026243Mine's on powersave by default, and it resets after every boot. I haven't given enough of a shit to invest the time to figure out how to fix this. I just use cpu-power-gui every time i notice my cpu freq is too low while doing something that needs my cpu. I can do most things on powersave without any issues at all on a ryzen 5 pro 4650. Unless I need to use 100% of the cpu, it's really not necessary to change to ondemand, though I set it every time I notice it's in powersave.
I had a similar discovery going into my bios and finding that the fans were set to "quiet" for at least a year. I tried every other relevant setting under the sun and had just accepted that my laptop was shittier than the specs suggested. Then my FPS tripled on average.
>>108026243wow i ran that command and mine was on powersave too. so that's why it was running slower than my other comp that had a slightly worse chip>>108026270this fixed itbut like this anon (>>108026702), it reset after boothow to make permsstartup script?btw whats the best place to put a startup script if sorunning mint btw
>>108026909There's a systemd service, but that didn't do anything for me.
>>108027012systemd bros, our response??
>>108026243Not a problem on a traditional Gentoo install since you configure your kernel and get to see the CPU governor setting.Just being aware of the CPU governor is enough. If you know it's a thing you have to deal with then you'll go out of your way to manage it.
Huh, mine is on powersave too but I never noticed any slowness or lag. Does this setting actually matter, and if so, why did nothing mention it until now?If I set power to performance on KDE I still see the same governor as well. After looking at the arch wiki this looks like a can of worms, and a good cpu should be auto-adjusting on demand even if you have powersave. I think.>https://wiki.archlinux.org/title/CPU_frequency_scaling#Scaling_governorsMaybe your firmware is just fucked, at least you found a fix I guess?
>>108028219You're just plain wrong, pal. Powersave does autoadjust. It just caps the cpu frquency to save power.
>>108026243Thats like the Linux version of people complaining about slow Windows when their laptop is in powersaving mode. Linus Tech Tips even made a whole video where he made this mistake comparing a Windows laptop in powersave mode to a mac.
>>108028387Oh wait it was the mac in low power mode. Don't know if I just mixed it up or he also had another video where he had a windows laptop in powersave mode.
>>108026290lot of distros do that by default now, it's annoying
>>108028219its a lie, nonny....
>>108026290most distro maintaimers have kernel defaults that conform to their ideal use case and they also think that sealevels rise ai destroys water and and paying al gore money wil fix global warming
>>108026290On Debian this is default.And it probably saves a ton of CO2 from idiots who don't know how shit works.
>>108026243Why does your cpu have a governor? How’d he get in there?
>>108028581linux kernel hardware scheduler, retard
>>108028607He has a scheduler too? There are two people in there?
>>108028613
>>108028628Huh?
>>108028642
i wish i could be entertained with such drivel im glad youre happy anon dont forget tour homework monday
>>108028671Bro I’m at the end of doing 4 12 hour shifts in a row. I’m delirious and pretending to be retarded is really funny to me right now.
Powersave ruines everything (especially Wayland) on Intel laptops, powersave does not mean “reasonable low power”. It means:- CPU sticks to very low clocks- Turbo boosts are delayed or never happen- Scheduler latency skyrockets- Interrupt handling gets sluggishAnd causes input lag, stutter under short CPU spikes, audio crackles, janky shit. Wayland in particular is very sensitive to scheduler latency, so once your CPU was allowed to ramp instantly.
>>108028935Why is a modern display server designed around making use of gpu acceleration so bottlenecked by the CPU while X ,which was designed before GPUs were a thing, isn't?
>>108028935not on my laptop beacuse i'm using intel_psave scaling driver
>>108026243TLP has CPU_SCALING_GOVERNOR_ON_AC and CPU_SCALING_GOVERNOR_ON_BAT options you can set. Does anyone actually use it with a desktop though?
>>108028546>>108028481wtf why? did a gaggle of tree huggers invade open sores?
>>108029283>he doesn't know
>>108026243so laptop users just supposed to tolerate the shitty input lag and stuttering?
>>108030240it's necessary to stop the rampant keylogging on linux desktops
>>108028581governator*
>>108026243If you're running a modern Intel or AMD CPU and kernel then it uses its own hardware based active scaling driver backend it doesn't make that much of a difference compared to legacy kernel software scaling governers
>Both Intel and AMD define a way to have the CPU decide its own speed based on (1) a performance range from the system and (2) a performance/power hint specifying the preference. The fully-autonomous mode is activated when:>amd_pstate is set to "active"—requires CPPC support in both the CPU and BIOS,>intel_pstate is set to "active" and hardware P-state (HWP) is available (i.e. Sandy Bridge and newer)—works out-of-the-box.>The most important feature of active governing is that only two governors appear available, powersave and performance. They do not work at all like their normal counterpart, however: these levels are translated into an Energy Performance Preference hint for the CPU's internal governor. As a result, they both provide dynamic scaling, similar to the schedutil or ondemand generic governors respectively, differing mostly in latency. cat /sys/devices/system/cpu/amd_pstate/statusactive
cat /sys/devices/system/cpu/amd_pstate/statusactive
I like the powersave governor it stops my fans from being so loud when compiling :)It takes longer but I compile at night anyway
>Linux Moment
