Community
Participate
Working Groups
The swapper (idle process) is often part of a critical path. But it makes no sense, as the critical path is supposed to be the path that we can shorten to improve the performance of the thread. There's probably another path that was not picked up by the algorithm that is more critical. So the algorithm should be made to ignore the special swapper process. Or else there may be something missing in the trace to make a good choice. In which case, the user should be warned, because putting swapper in the critical path is confusing.
To be clear, the swapper can be part of the critical path if we have ran out of ram and are using the virtual mem, no?
I don't know, but if so, that should be made clear that memory ran out at this point, which still makes swapper a special case.
I would say swapper is a special case with the Linux kernel since we know what it does... In this case we would need a supplemental swapper analysis to complement the trace. We can just dummy it out, but I think if we do that, we should have the option of bringing it back.
@Mathew I have a patch for that, enabled/disabled is coming too
Created attachment 270921 [details] Screenshot that shows the swapper issue
Ok, I have couple of questions: 1- would it be more interesting to sort the entries by coupling like the optimize button? 2- would it be more interesting to have a "filter" option that can remove all processes you don't like?
