[ Thanks to Jeremy
Andrews for this link. ]
“Rick Lindsley recently uploaded some interesting comparisons of
scheduler latency between 2.6.0-test5, -test5-mm3, -test6, and
-test6-mm1 with four different benchmarks. The benchmarks used were
Volanomark, SPECjbb, SPECdets, and the Kernbench kernel compilation
scripts. His summmary looks at how performance has changed, how
scheduler behavior has changed, and how these changes affect the
different benchmarking tools used. He explains:“‘High latency would usually indicate congested runqueues. High
runslices generally indicates workloads that were cpu-bound.
Different benchmarks have different ‘normal’ behavior, however.
Although results were gathered, most benchmarks were run in an
abbreviated manner to see trends and characteristics rather than
run full out, fully tuned, to get valid test results…'”