Does the kernel scheduler even matter???

Posted Sep 7, 2009 13:46 UTC (Mon) by mingo (subscriber, #31122)
In reply to: Does the kernel scheduler even matter??? by mjthayer
Parent article: BFS vs. mainline scheduler benchmarks and measurements

For many things the process scheduler does matter.

For most desktop things, the IO scheduler, the file system and the VM has a far bigger role.

To measure latencies, there's the latencytop tool from Arjan that can give a first-level guess about what the main source of latencies is.

If it's IO latencies then blktrace can be used to pin them down more precisely.

If it's indeed the process scheduler that is causing latencies, the latency tracer can be used to pin down the reason more precisely. On the lowest level the function tracer can be used too, for harder cases. There's also a lot of built-in statistics, tracepoints and in .31 based kernels also performance counters that can help in the pinning down of such bugs.

to post comments

Does the kernel scheduler even matter???

Posted Sep 10, 2009 20:54 UTC (Thu) by ajb (subscriber, #9694) [Link]

The scheduler could still help more under conditions of VM stress. For example, on my netbook, which thrashes when you run firefox + anything, I literally run killall -STOP firefox-bin; killall -CONT other-app when I want to switch between them. This is a lot more convenient than quitting and restarting each app, which otherwise I would have to do. I imagine there might be some less manual way to achieve the same thing by building some more smarts into the scheduler/VM to achieve the same effect. Possibly with help from userspace.