|| ||Linus Torvalds <torvalds-AT-linux-foundation.org> |
|| ||Mike Galbraith <efault-AT-gmx.de> |
|| ||Re: [RFC/RFT PATCH v3] sched: automated per tty task groups |
|| ||Sun, 14 Nov 2010 19:12:27 -0800|
|| ||Markus Trippelsdorf <markus-AT-trippelsdorf.de>,
Oleg Nesterov <oleg-AT-redhat.com>,
Peter Zijlstra <a.p.zijlstra-AT-chello.nl>,
Mathieu Desnoyers <mathieu.desnoyers-AT-efficios.com>,
Ingo Molnar <mingo-AT-elte.hu>,
|| ||Article, Thread
On Sun, Nov 14, 2010 at 5:13 PM, Mike Galbraith <firstname.lastname@example.org> wrote:
> Which is what I just did. If the oddball case isn't a big deal, the
> patch shrinks, which is a good thing. I just wanted to cover all bases.
Yeah. And I have to say that I'm (very happily) surprised by just how
small that patch really ends up being, and how it's not intrusive or
I'm also very happy with just what it does to interactive performance.
Admittedly, my "testcase" is really trivial (reading email in a
web-browser, scrolling around a bit, while doing a "make -j64" on the
kernel at the same time), but it's a test-case that is very relevant
for me. And it is a _huge_ improvement.
It's an improvement for things like smooth scrolling around, but what
I found more interesting was how it seems to really make web pages
load a lot faster. Maybe it shouldn't have been surprising, but I
always associated that with network performance. But there's clearly
enough of a CPU load when loading a new web page that if you have a
load average of 50+ at the same time, you _will_ be starved for CPU in
the loading process, and probably won't get all the http requests out
So I think this is firmly one of those "real improvement" patches.
Good job. Group scheduling goes from "useful for some specific server
loads" to "that's a killer feature".
to post comments)