Re: Epic regression in throughput since v2.6.23
From: Mike Galbraith
Date: Mon Sep 14 2009 - 02:16:58 EST
On Sun, 2009年09月13日 at 21:17 +0200, Mike Galbraith wrote:
>
Anyway, I'm thinking of tracking forks/sec as a means of detecting the
>
fork/exec load. Or, maybe just enable it when there's > 1 buddy pair
>
running.. or something. After all, NEXT_BUDDY is about scalability, and
>
make -j4 on a quad surely doesn't need any scalability help :)
But, this buddy vs fork/exec thing is not at all cut and dried. Even
with fork/exec load being the primary CPU consumer, there are genuine
buddies to worry about when you've got a GUI running, next/last buddy
can reduce the chances that an oinker slips in between X and client.
Ponder...
(oil for rusty old ponder machine welcome, gears grinding)
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/