4 ms·
Android does exactly that. (Called foreground processes.) It breaks things that require steady throughput and low latency, like media handling. Everywhere where
by AstralStorm 9y ago
Android does exactly that. (Called foreground processes.) It breaks things that require steady throughput and low latency, like media handling. Everywhere where you need a wake-up estimate and are using a dumb controller to get runtime, you get immense noise.
It is also highly unnecessary. If you have preemptible kernel, standard task start handling puts new tasks on top of their parents tree of tasks to be scheduled. (Tunable in sysfs.) If there is no restart, boost shouldn't be necessary on a preemptible kernel anyway, especially rt enabled ones, as lock holders on input will get woken up.
About the only place where it is useful is in boosting cpu clocks. This is also where it breaks timings the most.
- bjackman 9y ago> About the only place where it is useful is in boosting cpu clocks. This is true, but it is still absolutely critical for making Android usable. If you disable boosting i.e. allow tasks to take several frame refresh periods to accumulate load and bring the CPU freq up, you get a really painful UX.
- AstralStorm 9y agoNot really. 90+% of the time touch screen process gets the cpu boosted before you're even done touching the screen with modern ondemand coufreq. (I mean like 4.12 or newer) Try it out one of these days, but don't forget you can tweak sampling periods. Conservative cpufreq uses load. Ondemand only sort of does. The problem still remains getting predictable tick timings working well. (not missing deadlines)