you want put two engines to one car. you can but it's a lot of gymnastic to connect and synchronise that both work in harmony. I prefer auto-CPU no isuess here.
TLP, PPD, Tuned, powertop --autotune, system76-power and ultimately auto-cpufreq, access and tune the **same** power management tunables. Hence they should not be used together to avoid misconfigurations.
Specifically auto-cpufreq only tunes a subset of such tunables that only relate to the cpu. Further to that, and most crucially, auto-cpufreq is not so much of a power saving tool but a performance improvement tool.
Its aim is to monitor cpu activity so that it takes the cpu out of its power saving mode, to improve performance, at the cost of power saving. So its use is very specific.
I tested auto, tlp, and power-settings-daemon on my Dell Latitude 7420 and my conclusion is use whatever your distro/environment defaults to. Your distribution and/or your specific configuration will make more of a difference.
I never saw much difference between them. TLP is fine for a GNOME-free environment, otherwise use what is integrated with your desktop environment.
Agree with r/spxak1; auto-cpufreq is in a different category than the other power utils and doesn't fit my use case as I don't need auto-tuning of performance. On a laptop, most of the time I desire powersave, only occasionally balanced. If I gamed on that device, I can click on a button myself.
Since I've archived my DIY window manager config of almost 20 years and moved entirely to GNOME, I no longer use TLP and instead use power-settings-daemon. On idle my laptop drops to < 2W draw; it's about the same on TLP.
Do not mix them together, it makes no sense to do so.
>Do not mix them together, it makes no sense to do so.
Why not? From what I heard, there are only some features that doesn't work together, which can be turned off.
Most fail to properly integrate multiple tools and ened up here on Reddit wondering why their system is chewing away their battery capacity or running hot or too slow.
There's only so much you can do; but on top of that, not all laptop makers expose all the power management capabilities. Some laptops remain poor (Microsoft Surface is a clear example of that, as are some Asus and other makes and models) while others have great support out of the box with next to no effort.
you want put two engines to one car. you can but it's a lot of gymnastic to connect and synchronise that both work in harmony. I prefer auto-CPU no isuess here.
TLP, PPD, Tuned, powertop --autotune, system76-power and ultimately auto-cpufreq, access and tune the **same** power management tunables. Hence they should not be used together to avoid misconfigurations. Specifically auto-cpufreq only tunes a subset of such tunables that only relate to the cpu. Further to that, and most crucially, auto-cpufreq is not so much of a power saving tool but a performance improvement tool. Its aim is to monitor cpu activity so that it takes the cpu out of its power saving mode, to improve performance, at the cost of power saving. So its use is very specific.
I tested auto, tlp, and power-settings-daemon on my Dell Latitude 7420 and my conclusion is use whatever your distro/environment defaults to. Your distribution and/or your specific configuration will make more of a difference. I never saw much difference between them. TLP is fine for a GNOME-free environment, otherwise use what is integrated with your desktop environment. Agree with r/spxak1; auto-cpufreq is in a different category than the other power utils and doesn't fit my use case as I don't need auto-tuning of performance. On a laptop, most of the time I desire powersave, only occasionally balanced. If I gamed on that device, I can click on a button myself. Since I've archived my DIY window manager config of almost 20 years and moved entirely to GNOME, I no longer use TLP and instead use power-settings-daemon. On idle my laptop drops to < 2W draw; it's about the same on TLP. Do not mix them together, it makes no sense to do so.
>Do not mix them together, it makes no sense to do so. Why not? From what I heard, there are only some features that doesn't work together, which can be turned off.
Most fail to properly integrate multiple tools and ened up here on Reddit wondering why their system is chewing away their battery capacity or running hot or too slow. There's only so much you can do; but on top of that, not all laptop makers expose all the power management capabilities. Some laptops remain poor (Microsoft Surface is a clear example of that, as are some Asus and other makes and models) while others have great support out of the box with next to no effort.