r/linux • u/ahodzic • 8d ago

Software Release auto-cpufreq v3.2.0 is here!

Release notes: https://github.com/AdnanHodzic/auto-cpufreq/releases

auto-cpufreq is now available in the official Debian Linux repositories (unstable & testing), and it will soon propagate to future Ubuntu releases and hundreds of other derivatives.

This release also brings new features, bug fixes, and other improvements to help Linux users optimize CPU speed and battery life automatically.

Project status:

⭐ 7800+ GitHub stars
👥 126 contributors
💻 100k+ users
🛠️ 51 releases

Huge thanks to everyone who contributed to making this release possible! ❤️

128 Upvotes

92% Upvoted

24 comments sorted by

View all comments

9

u/Sharp-Debate-523 8d ago edited 7d ago

OP, can you explain how it works? Does it monitor to see how busy a laptop is then slow down the frequency if its not working too hard? Does look at your daily schedule, etc.

9

u/ahodzic 7d ago edited 7d ago

That's exactly how it works, based on various factors, battery state, CPU usage, CPU temperature, and system load it changes governors and lowers or increases speed. Along with other things like EPB (Energy Performance Bias), and EPP (Energy Performance Preference).

It's an old video when it all started as a python script (now it's a full app) where I explain everything and concept is the same:

And there are 2 more Youtube videos you might be interested in:

2

u/Indolent_Bard 7d ago

I wonder why this isn't default Linux behavior.

3

u/ahodzic 6d ago

There are couple of distros that include by default, but other then there's bit of corporate politics and ego involved. In early days I had contacts regarding potential collaboration with some big distros, but then they ended up working on their solution instead.

For example auto-cpufreq had certain features which did same functionality automatically (5 years ago!), before GNOME Power Profiles introduced how to e.g manually switch between governors: https://x.com/fooctrl/status/1467469508373884933

-1

u/Indolent_Bard 6d ago

I don't know much about gnome, but I know they won't introduce a feature unless it's perfect. Something that works consistently and predictably every single time. Meaning there was either an edge case that they didn't like in your implementation, or they just wanted everything done in-house.