On my system, KDE's 3.5.5 Konqueror uses CPU time in a very strange way. It sleeps for about 60% of time, then does something CPU-intensive for 40%. Its interchanging sleeps/runs are quite short, so its priority is not lowered by the scheduler, and its CPU consumption has its visible impact on Mozilla Seamonkey 1.1.1 running in the nearby X session on the same CPU. Manual renicing of Konqueror to level 19 helps, but should not it be automatic ?
I wonder if this new scheduler can detect such "isochronous" CPU consumers and deal with them accordingly ?
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds