From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] prefer wakers -v2
Date: Fri, 16 Jan 2009 15:27:55 +0100 [thread overview]
Message-ID: <1232116075.6141.29.camel@marge.simson.net> (raw)
In-Reply-To: <20090114113917.199690328@chello.nl>
On Wed, 2009-01-14 at 12:39 +0100, Peter Zijlstra wrote:
> OK, so lets try this again...
I took tip out for a little test-drive. Mysql/pgsql+oltp showed no
effect vs 29.git beyond noise level, but cache hot make -j8 kbuild times
in an nfs4 mount show marked improvement.
2.6.29.git
real 6m29.291s
user 10m20.355s
sys 2m1.288s
2.6.29.tip
real 4m30.160s
user 10m26.115s
sys 2m3.088s
Wire saturates at ~4m, so there's still some room for improvement.
On the interactivity front, tip feels snappier, particularly when IO is
going on. One place that this is quite noticeable is reading lkml with
evolution while building a new kernel. I generally keep thread count
low when using evolution because IO makes it sluggish when deleting and
moving on to the next message. With tip, the evolution experience is
much improved.
-Mike
prev parent reply other threads:[~2009-01-16 14:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 11:39 [PATCH 0/2] prefer wakers -v2 Peter Zijlstra
2009-01-14 11:39 ` [PATCH 1/2] sched: introduce avg_wakeup Peter Zijlstra
2009-01-14 11:59 ` Peter Zijlstra
2009-01-14 12:03 ` Peter Zijlstra
2009-01-14 12:04 ` Peter Zijlstra
2009-01-14 12:05 ` Ingo Molnar
2009-01-14 13:20 ` Peter Zijlstra
2009-01-15 11:00 ` Ingo Molnar
2009-01-14 11:39 ` [PATCH 2/2] sched: prefer wakers Peter Zijlstra
2009-01-14 11:47 ` [PATCH 0/2] prefer wakers -v2 Ingo Molnar
2009-01-14 12:14 ` Mike Galbraith
2009-01-16 14:27 ` Mike Galbraith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1232116075.6141.29.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox