[chucky_z]

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.

[bcrl]

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.

[worthless-trash]

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.

[markhahn]

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.

[chucky_z]

I did the reverse, I needed something to keep CPUs pegged at 100% power all the time, and for some reason the boxes I was using at the time kept going 'no no it's ok I need to save power,' but that lead to really inconsistent performance. Tuned, in that environment, 'just worked' after I wrote a custom profile.

There was another issue I was able to fix with it in AWS, but I legitimately can't recall what it is.