Thank you for your incredibly thorough analysis of this. Since finding this via bug 2046470, I have tried, without success, to create a test to show any difference in performance or power or whatever between irqbalance enabled/disabled on my Ubuntu 20.04 test server.
While my vote carries little weight here, I give it anyhow:
A) Change it from an opt-out to an opt-in and remove the dependency
from ubuntu-standard
Mainly because, and from my own investigation, I agree with:
> To me this seems to be a perfect case for a few special images/deployments
> known to match the workload profile that needs this to enable it.
> It is also more likely that a professional admin of such a large scale machine
> (or cluster thereof) can make the opt-in decision and evaluation better than
> expecting every user of Ubuntu to think about an opt-out.
Thank you for your incredibly thorough analysis of this. Since finding this via bug 2046470, I have tried, without success, to create a test to show any difference in performance or power or whatever between irqbalance enabled/disabled on my Ubuntu 20.04 test server.
While my vote carries little weight here, I give it anyhow:
A) Change it from an opt-out to an opt-in and remove the dependency
from ubuntu-standard
Mainly because, and from my own investigation, I agree with:
> To me this seems to be a perfect case for a few special images/deployments
> known to match the workload profile that needs this to enable it.
> It is also more likely that a professional admin of such a large scale machine
> (or cluster thereof) can make the opt-in decision and evaluation better than
> expecting every user of Ubuntu to think about an opt-out.