Originally posted by ninez
View Post
That's what I assumed you meant by idle, namely, programs that were still in active memory but not actively processing.
Assuming the programs aren't just terribly written, or need to do synchronous logging even when idle (I think FF still does this), that percentage is likely due to RT_PREEMPT (I'd guess timer setup/breakdown is the main culprit which is why I mentioned slack timer...BTW, cgroup management is going to be easier to do than per proc... https://lkml.org/lkml/2011/10/11/246). However, if your system is working good enough, I sure as hell wouldn't screw with it My tuning experience has been very hit or miss. The problem, of course, is defining the problem and creating tests. Unfortunately, for ordinary desktop usage (i.e., encompassing more than irq request delay), it is very hard to measure, and people don't even agree what we should be measuring. If we did, there would be no ambiguity about which scheduler is better for general desktop usage
BTW, I don't recall if I told you but I had to uninstall that RT kernel I got from the stanford repos. It was wreaking a wide swathe of destruction all through my desktop.
Best/Liam
Comment