From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Borislav Petkov <bp@alien8.de>, Olivier Doucet <webmaster@ajeux.com>
Cc: linux-kernel@vger.kernel.org, Venkatesh Pallipadi <venki@google.com>
Subject: Re: Performance issue since 3.2.6
Date: Fri, 18 Jan 2013 22:46:32 +0100 [thread overview]
Message-ID: <2125649.yvtIPMVHz8@vostro.rjw.lan> (raw)
In-Reply-To: <20130118212447.GB3252@pd.tnic>
On Friday, January 18, 2013 10:24:48 PM Borislav Petkov wrote:
> Good description.
>
> I'm leaving the whole email in for reference, see below:
>
> On Fri, Jan 18, 2013 at 10:05:41PM +0100, Olivier Doucet wrote:
> > Hello,
> >
> > I think I found a performance issue in kernel. This problem was
> > introduced in 3.2.6 and is affecting all version, including 3.7.1
> > (latest tested).
> >
> > I measured several kernel builds with a homebrew LAMP platform
> > benchmark (250 runs, average value kept).
> >
> > Kernel 3.2.0 was on production so far, and I tried an upgrade to 3.7.1
> > (latest kernel at that time). No software other than the kernel was
> > modified. Kernel was built with the same .config file (new options
> > left with default value).
> > Difference in performance was quite huge :
> > Kernel 3.7.1 : ~ 3250 queries / second
> > Kernel 3.2.0 : ~ 4300 queries / second
> >
> > Yes, this is a 25% performance drop ...
> >
> > To narrow things down, I tested several kernels :
> > 3.2.0 to 3.2.5 : OK
> > 3.2.6, 3.2.11, 3.2.28, 3.2.36, 3.7.1 : PERFORMANCE DROP
> > On faulty kernels, performance drop is always the same.
> >
> > At this step, I know that bug was introduced in version 3.2.6. I then
> > used git bisect (amazing tool btw) to find the faulty commit :
> > f51d67a64f32cd81ea8b67ca964fb7cf7e783b2e PM / QoS: CPU C-state
> > breakage with PM Qos change
> >
> > Next test : I used a 3.2.6 and reverted this patch : performance was
> > back to normal.
> > I also reverted this patch on 3.2.36 (latest 3.2.X), and performance
> > was also OK. I was unable to revert this patch on 3.7.1 (structure of
> > the source file /include/linux/pm_qos.h changed too heavily).
> >
> > Kernel was built on a x86_64 platform with binutils 2.19.1 and gcc 4.4.0.
> > .config file used : https://gist.github.com/4567342
> > Benchmark was run on a dual CPU INTEL L5630 with 4GB of RAM
> >
> > What can I do to resolve this problem ?
>
> Btw, the commit-id you've given is the stable commit-id but this is
> still ok, the mainline commit is mentioned in the commit message and is:
>
> commit d020283dc694c9ec31b410f522252f7a8397e67d
> Author: Venkatesh Pallipadi <venki@google.com>
> Date: Fri Feb 3 22:22:25 2012 +0100
>
> PM / QoS: CPU C-state breakage with PM Qos change
>
> So, let's invite the parties from the commit to CC, see what they have
> to say.
Thanks Boris!
Olivier, may I see the kernel .config file?
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-01-18 21:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 21:05 Olivier Doucet
2013-01-18 21:24 ` Borislav Petkov
2013-01-18 21:46 ` Rafael J. Wysocki [this message]
2013-01-18 21:43 ` Olivier Doucet
2013-01-18 22:17 ` Rafael J. Wysocki
2013-01-21 13:18 ` Olivier Doucet
2013-01-21 13:29 ` Rafael J. Wysocki
2013-01-21 14:26 ` Olivier Doucet
2013-01-21 22:49 ` Rafael J. Wysocki
2013-01-21 22:57 ` Olivier Doucet
2013-01-21 23:09 ` Rafael J. Wysocki
2013-01-31 15:15 ` Olivier Doucet
2013-02-12 21:09 ` Olivier Doucet
2013-05-17 18:17 ` Olivier Doucet
2013-05-17 19:50 ` Srivatsa S. Bhat
2013-05-17 23:51 ` Rafael J. Wysocki
2013-05-18 5:04 ` Srivatsa S. Bhat
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=2125649.yvtIPMVHz8@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=venki@google.com \
--cc=webmaster@ajeux.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
Powered by JetHome