From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: sysbench+mysql(oltp, readonly) 30% regression with 2.6.26-rc1
Date: Fri, 09 May 2008 10:23:27 +0200 [thread overview]
Message-ID: <1210321407.5285.0.camel@marge.simson.net> (raw)
In-Reply-To: <1210320160.13978.209.camel@twins>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
On Fri, 2008-05-09 at 10:02 +0200, Peter Zijlstra wrote:
> On Fri, 2008-05-09 at 09:58 +0200, Mike Galbraith wrote:
> > On Fri, 2008-05-09 at 09:50 +0200, Peter Zijlstra wrote:
> > > On Fri, 2008-05-09 at 09:32 +0200, Mike Galbraith wrote:
> > > > On Fri, 2008-05-09 at 08:51 +0200, Peter Zijlstra wrote:
> > > > > > > > -rc1. Do you have the fix below applied?
> > > > > > >
> > > > > > > Oooh - good catch, that seems to be a post -rc1 merge.
> > > > > > >
> > > > > > > Yes this is required.
> > > > >
> > > > > > With below patch+previous_fix_weight_calc, the result is improved, but is still
> > > > > > about 10% worse than the one of pure 2.6.26-rc1.
> > > > > > Number of threads: 16
> > > > > > read/write requests: 6104336 (50867.11 per sec.)
> > > > > >
> > > > >
> > > > > So puzzling - could you try -git + fix_weight_calc, as I think that is
> > > > > what Mike tested and proved good on his Quad.
> > > >
> > > > If he still has group scheduling enabled, my box agrees that there's a
> > > > regression. I got mysql running, and tested with group scheduling both
> > > > enabled and disabled, results attached. (for some reason, I can only
> > > > test up to 64 threads with mysql though)
> > >
> > > Hm, ok. Does the patch at hand improve or regress the group config for
> > > you?
> >
> > I'm testing got.today.
> >
> > You mean 46151122e0a2e80e5a6b2889f595e371fe2b600d?
>
> Exactly - Yanmin says it makes it worse for him, I'm wondering if you
> can see a similar problem with group scheduling enabled.
Nope, same fugly curve +-jitter.
-Mike
[-- Attachment #2: yy.pdf --]
[-- Type: application/pdf, Size: 17674 bytes --]
next prev parent reply other threads:[~2008-05-09 8:23 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
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 [this message]
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=1210321407.5285.0.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--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