From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Nicholas Miell <nmiell@comcast.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23
Date: Fri, 12 Oct 2007 07:46:15 +0200 [thread overview]
Message-ID: <20071012054615.GA22256@elte.hu> (raw)
In-Reply-To: <200710111916.23633.nickpiggin@yahoo.com.au>
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> ;) I think you snipped the important bit:
>
> "the peak is terrible but it has virtually no dropoff and performs
> better under load than the default 2.6.21 scheduler." (verbatim)
hm, i understood that peak remark to be in reference to FreeBSD's
scheduler (which the FreeBSD guys are primarily interested in
obviously), not v2.6.21 - but i could be wrong.
In any case, there is indeed a regression with sysbench and a low number
of threads, and it's being fixed. The peak got improved visibly in
sched-devel:
http://people.redhat.com/mingo/misc/sysbench-sched-devel.jpg
but there is still some peak regression left, i'm testing a patch for
that.
Ingo
next prev parent reply other threads:[~2007-10-12 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 20:54 Linux 2.6.23 Linus Torvalds
2007-10-10 6:12 ` Nicholas Miell
2007-10-10 10:14 ` Ingo Molnar
2007-10-11 1:20 ` Nicholas Miell
2007-10-11 2:34 ` Zhang, Yanmin
2007-10-11 13:32 ` Ingo Molnar
2007-10-11 9:16 ` Nick Piggin
2007-10-12 5:46 ` Ingo Molnar [this message]
2007-10-11 14:15 ` Nick Piggin
2007-10-12 12:21 ` Bill Davidsen
2007-10-10 7:44 ` René Rebe
2007-10-10 8:37 ` Alexey Dobriyan
2007-10-10 9:12 ` Michael Tokarev
2007-10-10 10:36 ` Alexey Dobriyan
2007-10-10 10:53 ` Jan Engelhardt
2007-10-10 11:13 ` Michael Tokarev
2007-10-10 19:14 ` Ingo Molnar
2007-10-10 19:26 ` Michael Tokarev
2007-10-10 20:04 ` Andi Kleen
2007-10-10 23:27 ` Krzysztof Halasa
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=20071012054615.GA22256@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=nmiell@comcast.net \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.