Package: wnpp Severity: wishlist X-Debbugs-Cc: Adnan Hodzic <ad...@hodzic.org>
* Package name : auto-cpufreq Version : 2.0.0 Upstream Contact: Adnan Hodzic <ad...@hodzic.org> * URL : https://github.com/AdnanHodzic/auto-cpufreq * License : LGPL-3 Programming Lang: Python Description : Automatic CPU speed & power optimizer Automatic CPU speed & power optimizer for, Linux based on active monitoring of a laptop's battery state, CPU usage, CPU temperature and system load. Ultimately allowing you to improve battery life without making any compromises. Features: * Monitoring * Basic system information * CPU frequency (system total & per core) * CPU usage (system total & per core) * CPU temperature (total average & per core) * Battery state * System load * CPU frequency scaling, governor and turbo boost management based on * Battery state * CPU usage (total & per core) * CPU temperature in combination with CPU utilization/load (prevent overheating) * System load * Automatic CPU & power optimization (temporary and persistent) ---- I found this package through this post on Debian Planet: https://foolcontrol.org/?p=4603 This is a tool similar to already existing tools in Debian, specifically TLP. According to the auto-cpufreq author though: > Using tools like TLP can help in this situation with extending > battery life (which is something I used to do for numerous years), > but it also might come with its own set of problems, like losing > turbo boost. > > With that said, I needed a simple tool which would automatically > make "cpufreq" related changes, save battery like TLP, but let Linux > kernel do most of the heavy lifting. That's how auto-cpufreq was > born. > > Please note: auto-cpufreq aims to replace TLP in terms of > functionality and after you install auto-cpufreq it's recommended to > remove TLP. If both are used for same functionality, i.e: to set CPU > frequencies it'll lead to unwanted results like overheating. Hence, > only use both tools in tandem if you know what you're doing. So I'm not exactly clear on what the overlap between the two is, but I do feel there's some room in this space for another option. TLP is rather "heavy" in terms of the number of things it does, it's a rather big pill to swallow, with all sorts of pitfalls... I like the idea of having a simple, one-task-focused tool. I do not currently have the cycles to evaluate this any further, but would love to collaborate on further research when I have time. Otherwise, if anyone is interested in pursuing this any further, please go right ahead (but keep this bug in CC!).
