mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Branimir Maksimovic <branimir.maksimovic@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel 4.7rc3 - Performance drop 30-40% for SPECjbb2005 and SPECjvm2008 benchmarks against 4.6 kernel
Date: Wed, 22 Jun 2016 09:37:10 +0200	[thread overview]
Message-ID: <3abcc9e2-3598-1264-4ba7-8557b35bbc6f@gmail.com> (raw)

Could it be related to this:

https://www.phoronix.com/scan.php?page=news_item&px=P-State-Possible-4.6-Regression


On Thu, 16 Jun 2016 18:40:01 +0200
Jirka Hladky <jhladky@redhat.com> wrote:

 > Hello,
 >
 > we see performance drop 30-40% for SPECjbb2005 and SPECjvm2008
 > benchmarks starting from 4.7.0-0.rc0 kernel compared to 4.6 kernel.
 >
 > We have tested kernels 4.7.0-0.rc1 and 4.7.0-0.rc3 and these are as
 > well affected.
 >
 > We have observed the drop on variety of different x86_64 servers with
 > different configuration (different CPU models, RAM sizes, both with
 > Hyper Threading ON and OFF, different NUMA configurations (2 and 4
 > NUMA nodes)
 >
 > Linpack and Stream benchmarks do not show any performance drop.
 >
 > The performance drop increases with higher number of threads. The
 > maximum number of threads in each benchmark is the same as number of
 > CPUs.
 >
 > We have opened a BZ to track the progress:
 > https://bugzilla.kernel.org/show_bug.cgi?id=120481
 >
 > You can find more details along with graphs and tables there.
 >
 > Do you have any hints which commit should we try to reverse?
 >
 > Thanks a lot!
 > Jirka

             reply	other threads:[~2016-06-22  7:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22  7:37 Branimir Maksimovic [this message]
2016-06-22  8:25 ` Jirka Hladky
  -- strict thread matches above, loose matches on Subject: below --
2016-06-16 16:38 Jirka Hladky
2016-06-16 17:22 ` Peter Zijlstra
2016-06-16 23:04   ` Jirka Hladky
2016-06-21 13:17     ` Jirka Hladky
2016-06-22  7:16     ` Peter Zijlstra
2016-06-22  7:49       ` Peter Zijlstra
2016-06-22  7:54         ` Peter Zijlstra
2016-06-22  9:52           ` Jirka Hladky
2016-06-22 11:12             ` Peter Zijlstra
2016-06-22 12:37               ` Jirka Hladky
2016-06-22 12:46                 ` Jirka Hladky
2016-06-22 14:41                   ` Jirka Hladky
2016-06-22 20:59                     ` Peter Zijlstra
2016-06-22  8:20       ` Jirka Hladky
2016-06-23 18:33     ` Peter Zijlstra
2016-06-23 18:43       ` Peter Zijlstra
2016-06-24  7:44         ` Jirka Hladky
2016-06-24  8:08           ` Peter Zijlstra
2016-06-24  8:20             ` Jirka Hladky
2016-06-24 12:02           ` Peter Zijlstra
2016-06-24 12:09             ` Jirka Hladky
2016-06-24 12:30               ` Peter Zijlstra
2016-06-24 12:35               ` Jirka Hladky
2016-06-24 12:44             ` Vincent Guittot
2016-06-24 13:08               ` Jirka Hladky
2016-06-24 13:09               ` Peter Zijlstra
2016-06-24 13:23                 ` Vincent Guittot
2016-06-24 13:33                   ` Peter Zijlstra
2016-06-24 13:45                   ` Peter Zijlstra
2016-06-24 13:42               ` Peter Zijlstra
2016-06-24 15:54                 ` Peter Zijlstra
2016-06-24 22:13                   ` Jirka Hladky

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=3abcc9e2-3598-1264-4ba7-8557b35bbc6f@gmail.com \
    --to=branimir.maksimovic@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®