I've used `tuned` a lot. It's really extremely good for personal machines/workstations, and really okay for servers. In my case I'm almost 50/50 with it in professional cases, where 50% of the time I had a real good time with it, and 50% of the time I turned it off and used startup scripts (like cloud-init per-boot and whatnot).
Overall, I'd say give it a shot as it can be really powerful and I do actually like it. Don't be afraid to go 'no, I know how to do this better, myself' and turn it off though.
I disable it whenever setting up a new system. It gets irq bindings for networking wrong every single time, and moves irqs around in ways that defeats the whole point of having per CPU queues. Not sure why that behaviour is enabled by default as it makes no sense.
Please lodge a bug because I seem to think the same way but lack the larger deployment experience to explain how to do it more generally than my tiny use case.
It's easier to uninstall it. There's nothing good that tuned has ever done for me.
FYI: messing with irq bindings for per-cpu queues of nics has been a bug for at least 16 years depending on the nic. FYI: Intel launched the 82599 back in 2009.
Clueless software developers should not be messing with kernel settings like irq bindings. Software that does that is not worth my time.
I saw really big power savings when I started using TuneD. Such a huge upgrade for Linux users! From 8 months ago, going from 120 -> 85W. More recently got my desktop down to 65, yay.
https://news.ycombinator.com/item?id=42636350
There's also API compatibility with the power-profiles-daemon, which didn't ever help me that much (I'd also done some basic tuning myself), and which has been unmaintained for a while now. But there's still a variety of utilities which target the old ppd.
There is something a bit wacky about a performance service implemented in an interpreted language like Python whether it is tuned or auto-cpufreq. Tuned does seem to be as good as it gets for the moment.
x86 cpus don't have the power efficiency to do the work we now expect of them in thin and light laptops with difficult thermal constraints. You can push them one way or another. You can have them fast with a fan like a jet engine or you can have them cold and running like a 10 year old computer or put the dial somewhere inbetween but there is only so much you can do.
TuneD doesn't have throughput or latency requirements, it should just tell the kernel what to do, perfect for python. If it's installed with the system python it'll share pages well with other Python applications.
And x86 not being power efficient is hardly true for the modern AMD mobile chips, it's not quite the "iPad" experience but it's very good. Comparing to Apple is unfair IMHO since M* is essentially an iPhone CPU with a souped up power budget, many years of optimization across both hardware, kernel and userspace that we don't have.
But when the whole Python interpreter machinery has to run in the background, that will prevent your system from going to lower power states more often.
“It does not matter for this case” times 100 is how we get these power-hungry systems.
Apple and many arm mobile platforms also have a mix of performance and efficiency cores so it seems to be a proven approach. I guess it comes down to implementation. Intel's efficiency cores by themselves (eg N series) apparently make nice little appliances, often better value than something like a RPi. I don't know how much they help their higher performance devices conserve energy.
I have one of Intel's old desktop class processors in a refurbished ex-office mini-desktop plugged into a power meter running a few services for the household and the idle usage isn't terrible. I don't understand why my laptop doesn't run colder and longer given the years of development between them.
There is also the race to idle strategy where you spike the performance cores to get back to idle which probably works well with a lot of office usage but not so well with something more demanding like games or benchmarks.
Given how much effort many people have put into combatting the trailing capital letter 'D' habit, including with one particular piece of RedHat software from 2010, it is interesting to see RedHat a couple of years earlier embracing the style.
Although all of the commands and files are all-lowercase: tuned.
The other amusing thing is the spanner in the icon, with the narrow jaws and mouth that is not angled. There are Apple pundits who insist that spanners do not look like that, and that Apple Has Got It Wrong. Of course, spanners can and do look like that.
It is probably lucky for RedHat that it does not have similar pundits. (-:
Hmm, started looking into this and realized I already had tlp running, and that supports limiting maximum charge on the battery in the laptop. I didn't seem to see anything equivalent in the tuned documentation, but I did see the presets… and finding things like SAP Hana makes me think this isn't aimed at laptops…
I've used `tuned` a lot. It's really extremely good for personal machines/workstations, and really okay for servers. In my case I'm almost 50/50 with it in professional cases, where 50% of the time I had a real good time with it, and 50% of the time I turned it off and used startup scripts (like cloud-init per-boot and whatnot).
Overall, I'd say give it a shot as it can be really powerful and I do actually like it. Don't be afraid to go 'no, I know how to do this better, myself' and turn it off though.
I disable it whenever setting up a new system. It gets irq bindings for networking wrong every single time, and moves irqs around in ways that defeats the whole point of having per CPU queues. Not sure why that behaviour is enabled by default as it makes no sense.
Please lodge a bug because I seem to think the same way but lack the larger deployment experience to explain how to do it more generally than my tiny use case.
It's easier to uninstall it. There's nothing good that tuned has ever done for me.
FYI: messing with irq bindings for per-cpu queues of nics has been a bug for at least 16 years depending on the nic. FYI: Intel launched the 82599 back in 2009.
Clueless software developers should not be messing with kernel settings like irq bindings. Software that does that is not worth my time.
Complaining here won't improve the situation, filing a bug might.
We used to call them script kiddies. Running stuff without understanding what's happening and why.
What did you accomplish with it?
Another answer talks about saving 40W. Why not? But it's not much in a normal power-cost environment.
I saw really big power savings when I started using TuneD. Such a huge upgrade for Linux users! From 8 months ago, going from 120 -> 85W. More recently got my desktop down to 65, yay. https://news.ycombinator.com/item?id=42636350
There's also API compatibility with the power-profiles-daemon, which didn't ever help me that much (I'd also done some basic tuning myself), and which has been unmaintained for a while now. But there's still a variety of utilities which target the old ppd.
There is something a bit wacky about a performance service implemented in an interpreted language like Python whether it is tuned or auto-cpufreq. Tuned does seem to be as good as it gets for the moment.
x86 cpus don't have the power efficiency to do the work we now expect of them in thin and light laptops with difficult thermal constraints. You can push them one way or another. You can have them fast with a fan like a jet engine or you can have them cold and running like a 10 year old computer or put the dial somewhere inbetween but there is only so much you can do.
TuneD doesn't have throughput or latency requirements, it should just tell the kernel what to do, perfect for python. If it's installed with the system python it'll share pages well with other Python applications.
And x86 not being power efficient is hardly true for the modern AMD mobile chips, it's not quite the "iPad" experience but it's very good. Comparing to Apple is unfair IMHO since M* is essentially an iPhone CPU with a souped up power budget, many years of optimization across both hardware, kernel and userspace that we don't have.
But when the whole Python interpreter machinery has to run in the background, that will prevent your system from going to lower power states more often.
“It does not matter for this case” times 100 is how we get these power-hungry systems.
What machinery?
I haven't tested Intel's efficiency cores (E-cores) myself - would these address the need for desktops/laptops?
Apple and many arm mobile platforms also have a mix of performance and efficiency cores so it seems to be a proven approach. I guess it comes down to implementation. Intel's efficiency cores by themselves (eg N series) apparently make nice little appliances, often better value than something like a RPi. I don't know how much they help their higher performance devices conserve energy.
I have one of Intel's old desktop class processors in a refurbished ex-office mini-desktop plugged into a power meter running a few services for the household and the idle usage isn't terrible. I don't understand why my laptop doesn't run colder and longer given the years of development between them.
There is also the race to idle strategy where you spike the performance cores to get back to idle which probably works well with a lot of office usage but not so well with something more demanding like games or benchmarks.
Thanks, that comment saved me from spending time looking at it.
What I'd like is a tool that can be run on a fresh linux install to show what's not working correctly and maybe some diagnostics. Does that exist?
Things like suspend to RAM/disk working, GPU performance is reasonable, WiFi and disk speeds aren't slower than expected.
> Things like suspend to RAM [...] working
If you're on and AMD laptop then suspend to ram can be tested with amd-debug-tools[0].
> WiFi
Here[1] is a list of public iperf3 servers. You can test your connection speed with (change host name and port to appropriate server):
You can also launch your own server so you're not limited by your internet speed (I usually run one on my router):one hot tip is that tuned has a translation tool for power-profiles-daemon, meaning you can change the profile via gnome / kde
https://archlinux.org/packages/extra/any/tuned-ppd/
Given how much effort many people have put into combatting the trailing capital letter 'D' habit, including with one particular piece of RedHat software from 2010, it is interesting to see RedHat a couple of years earlier embracing the style.
Although all of the commands and files are all-lowercase: tuned.
The other amusing thing is the spanner in the icon, with the narrow jaws and mouth that is not angled. There are Apple pundits who insist that spanners do not look like that, and that Apple Has Got It Wrong. Of course, spanners can and do look like that.
It is probably lucky for RedHat that it does not have similar pundits. (-:
* https://news.ycombinator.com/item?id=45021826
Hmm, started looking into this and realized I already had tlp running, and that supports limiting maximum charge on the battery in the laptop. I didn't seem to see anything equivalent in the tuned documentation, but I did see the presets… and finding things like SAP Hana makes me think this isn't aimed at laptops…
echo 80 | sudo sponge /sys/class/power_supply/BAT0/charge_control_end_threshold
https://manpages.debian.org/testing/moreutils/sponge.1.en.ht... good for privilege escalated pipe to file :)