>AFAICT our kernel config is set to performance - why not just set it to ondemand?
So from my understanding, the point of the ondemand script is really so we can have boot set to performance, and then switch later to something that saves more power. The goal is boot performance so If we survey machines and find that's it's harming or negligible to boot performance that makes a compelling argument against it - correct? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1503773 Title: Drop ondemand init script Status in sysvinit package in Ubuntu: Confirmed Bug description: Ondemand init script is not inherited from Debian, it's an Ubuntu specific change. Some reasons to get rid of it: On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance with no ability to change frequency.. In the init script we don't run this for android Ondemand is already on by default! Why don't we just always use whatever is that kernel's default? There are a number of other reported problems with it: https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1503773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
