And yet you can make the exact same case for schedulers as security, you
can quantify the behavior, but if your only choice is A it doesn't help
to know that B is better.
You say "performance" as if it had universal meaning. In truth people
want to optimize for total tps (servers), or responsiveness on the human
scale (mail, dns, nntp servers), or perceived smoothness (with many
threads updating a display to slow with load rather than start visibly
jumping the motion from one to another), or very short term response
(-rt patches). People want very different behavior under the same load,
and that is what *they* call "performance," namely best delivery of
what's important. The numbers are "hard science" but the choice of which
numbers are important is still "people wanking around with their opinions".
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
-
