From: Nicholas Miell <nmiell@comcast.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.23
Date: Wed, 10 Oct 2007 18:20:42 -0700 [thread overview]
Message-ID: <1192065642.2695.9.camel@entropy> (raw)
In-Reply-To: <20071010101452.GA25433@elte.hu>
On Wed, 2007-10-10 at 12:14 +0200, Ingo Molnar wrote:
> * Nicholas Miell <nmiell@comcast.net> wrote:
>
> > Does CFS still generate the following sysbench graphs with 2.6.23, or
> > did that get fixed?
> >
> > http://people.freebsd.org/~kris/scaling/linux-pgsql.png
> > http://people.freebsd.org/~kris/scaling/linux-mysql.png
>
> as far as my testsystem goes, v2.6.23 beats v2.6.22.9 in sysbench:
>
> http://redhat.com/~mingo/misc/sysbench.jpg
That's nice to know. Note that I'm not actually involved in any of these
tests, just a somewhat interested bystander.
>
> As you can see it in the graph, v2.6.23 schedules much more consistently
> too. [ v2.6.22 has a small (but potentially statistically insignificant)
> edge at 4-6 clients, and CFS has a slightly better peak (which is
> statistically insignificant). ]
>
> ( Config is at http://redhat.com/~mingo/misc/config, system is Core2Duo
> 1.83 GHz, mysql-5.0.45, glibc-2.6. Nothing fancy either in the config
> nor in the setup - everything is pretty close to the defaults. )
>
> i'm aware of a 2.6.21 vs. 2.6.23 sysbench regression report, and it
> apparently got resolved after various changes to the test environment:
>
> http://jeffr-tech.livejournal.com/10103.html
>
> " [<CFS>] has virtually no dropoff and performs better under load than
> the default 2.6.21 scheduler. " (paraphrased)
>
> (The new link you posted, just a few hours after the release of v2.6.23,
> has not been reported to lkml before AFAICS - when did you become aware
> of it? If you learned about it before v2.6.23 it might have been useful
> to report it to the v2.6.23 regression list.)
According to my IRC logs, Jeffr pasted the URL at Oct 09 22:53:56 PDT.
He says he tried to contact you early in CFS's development, but got no
reply.
> At a quick glance there are no .configs or other testing details at or
> around that URL that i could use to reproduce their result precisely, so
> at least a minimal bugreport would be nice.
>
AFAICT, the configuration is described in
http://people.freebsd.org/~kris/scaling/mysql.html
--
Nicholas Miell <nmiell@comcast.net>
next prev parent reply other threads:[~2007-10-11 1:20 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 [this message]
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
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=1192065642.2695.9.camel@entropy \
--to=nmiell@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox