From: Mike Galbraith <efault@gmx.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1
Date: Thu, 08 May 2008 10:00:17 +0200 [thread overview]
Message-ID: <1210233617.4895.6.camel@marge.simson.net> (raw)
In-Reply-To: <1210228531.3453.124.camel@ymzhang>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
On Thu, 2008-05-08 at 14:35 +0800, Zhang, Yanmin wrote:
> On Wed, 2008-05-07 at 18:26 +0200, Peter Zijlstra wrote:
> > On Wed, 2008-05-07 at 12:55 +0800, Zhang, Yanmin wrote:
> > > Comparing with kernel 2.6.25, sysbench+mysql(oltp, readonly) has many
> > > regression with 2.6.26-rc1.
> > >
> > > 1) 8-core stoakley: 28%;
> > > 2) 16-core tigerton: 20%;
> > > 3) Itanium Montvale: 50%.
> > >
> > > Bisect located below patch.
> > >
> > > 8f1bc385cfbab474db6c27b5af1e439614f3025c is first bad commit
> > > commit 8f1bc385cfbab474db6c27b5af1e439614f3025c
> > > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > > Date: Sat Apr 19 19:45:00 2008 +0200
> > >
> > > sched: fair: weight calculations
> > >
> > > In order to level the hierarchy, we need to calculate load based on the
> > > root view. That is, each task's load is in the same unit.
> > >
> > >
> > >
> > > After I manually reverted the patch against 2.6.26-rc1 while fixing a couple of
> > > conflictions/errors, sysbench oltp regression became less than 3% on 8-core
> > > stoakley.
> >
> > Does this patch help?
> With the patch, oltp testing result is about 50% worse than the one of pure
> 2.6.26-rc1.
Hm. I was doing some sysbench+postgress(oltp, ro) testing on my little
Q6600 box this morning, and saw a different picture.
In attached pdf, .bkl refers to Linus' BKL patch, .weight is the weight
fix, both are applied to git.today. The script I used is also attached.
-Mike
[-- Attachment #2: xx.pdf --]
[-- Type: application/pdf, Size: 18377 bytes --]
[-- Attachment #3: sysbench.test --]
[-- Type: application/x-shellscript, Size: 2468 bytes --]
next prev parent reply other threads:[~2008-05-08 8:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 4:55 sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1 Zhang, Yanmin
2008-05-07 9:16 ` Ingo Molnar
2008-05-07 9:33 ` Zhang, Yanmin
2008-05-07 10:40 ` Ingo Molnar
2008-05-07 16:26 ` Peter Zijlstra
2008-05-08 6:35 ` Zhang, Yanmin
2008-05-08 8:00 ` Mike Galbraith [this message]
2008-05-08 8:46 ` Ingo Molnar
2008-05-08 9:25 ` Ingo Molnar
2008-05-08 10:00 ` Mike Galbraith
2008-05-08 9:37 ` Mike Galbraith
2008-05-08 9:01 ` Zhang, Yanmin
2008-05-08 9:13 ` Peter Zijlstra
2008-05-08 9:15 ` Mike Galbraith
2008-05-08 9:22 ` Zhang, Yanmin
2008-05-08 9:23 ` Peter Zijlstra
2008-05-09 1:16 ` Zhang, Yanmin
2008-05-09 6:51 ` Peter Zijlstra
2008-05-09 7:32 ` Mike Galbraith
2008-05-09 7:50 ` Peter Zijlstra
2008-05-09 7:58 ` Mike Galbraith
2008-05-09 8:02 ` Peter Zijlstra
2008-05-09 8:23 ` Mike Galbraith
2008-05-09 9:47 ` Mike Galbraith
2008-05-09 7:59 ` Mike Galbraith
2008-05-09 8:10 ` Peter Zijlstra
2008-05-09 8:25 ` Mike Galbraith
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=1210233617.4895.6.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.com \
/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