From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Lorenzo Allegrucci <l.allegrucci@gmail.com>,
Bj?rn <askadar@gmail.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: 2.6.23 performance regression
Date: Wed, 31 Oct 2007 10:55:17 +0100 [thread overview]
Message-ID: <20071031095517.GA5817@elte.hu> (raw)
In-Reply-To: <200710311319.54210.nickpiggin@yahoo.com.au>
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> On Tuesday 30 October 2007 18:54, Lorenzo Allegrucci wrote:
> > Hi, sorry if this is a faq but reading
> > http://people.freebsd.org/~kris/scaling/7.0%20Preview.pdf (slides 17,
> > 18)
> > looks like 2.6.23 is having a performance regression on MySQL and
> > PostgreSQL benchmarks. Has anyone investigated these?
>
> I think Ingo was looking into them. I'm just in the middle of building
> a new setup to investigate some performance issues too, so I hope to
> look at this.
>
> Apparently it did go unnoticed during CFS testing, unfortunately.
> Although now it has been brought to light, I think 2.6.24 is supposed
> to be better (although it now gets worse on other things).
yep. For those who fear the 1 million lines of code flux of 2.6.24,
here's a backport of the scheduler changes to 2.6.23:
http://people.redhat.com/mingo/cfs-scheduler/devel/sched-cfs-v2.6.23.1-v22.1-rc0.patch
Lorenzo, could you please try that report back your reports? Thanks,
Ingo
prev parent reply other threads:[~2007-10-31 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 7:54 2.6.23 performance regression Lorenzo Allegrucci
2007-10-31 2:19 ` Nick Piggin
2007-10-31 9:55 ` Ingo Molnar [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=20071031095517.GA5817@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=askadar@gmail.com \
--cc=l.allegrucci@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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.