[j1elo]

I'm surprised they didn't go to a more clever solution such as "start loading it as soon as the most core components have already loaded, and CPU usage falls below 30% during 3 to 5 consecutive seconds".

That'd seem to me like a sweet spot between what was before (making the whole system startup slower), and what you mention will be now (probably making the first search to load noticeably slower).

[TillE]

With modern hardware and OSes the ideal answer is typically to run non-essential tasks exclusively on efficiency cores. So you leave the performance cores free to handle stuff that the user immediately cares about.

[viraptor]

If anyone wants to play with that, the "uclamp" interface is the "nice" that affects the scheduler / placement / energy use. Pipewire got a patch recently to keep the requested power low https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/70...