mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@techsingularity.net>
To: Jirka Hladky <jhladky@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Jakub Ra??ek <jracek@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"kkolakow@redhat.com" <kkolakow@redhat.com>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [SCHEDULER] Performance drop in 4.19 compared to 4.18 kernel
Date: Mon, 17 Sep 2018 14:06:29 +0100	[thread overview]
Message-ID: <20180917130629.nugwsgcsuoda6qf6@techsingularity.net> (raw)
In-Reply-To: <CAE4VaGDoxOQEhPYtVzEkNdrnFQ=Lnjj2is71ZYUBn_csUreoNA@mail.gmail.com>

On Fri, Sep 14, 2018 at 04:50:20PM +0200, Jirka Hladky wrote:
> Hi Peter and Srikar,
> 
> > I have bounced the 5 patches to you, (one of the 6 has not been applied by
> > Peter) so I have skipped that.
> > They can also be fetched from
> > http://lore.kernel.org/lkml/1533276841-16341-1-git-send-email-srikar@linux.vnet.ibm.com
> 
> I'm sorry for the delay, we have finally the results for the above
> kernel. The performance results look good compared to 4.19 vanilla and
> are about the same as Mel's sched-numa-fast-crossnode-v1r12 patch set
> for 4.18:
> 
> Compared to kernel-4.19.0-0.rc1.1
> 
>   * Improvement upto 20% for SPECjbb2005, SPECjvm2008 benchmarks
>   * Improvement upto 50% for stream benchmark
>   * Improvement upto 100% for the NAS benchmark (sp_C subtest, 8
> threads on 4 NUMA system with 4x E5-4610 v2 @ 2.30GHz, 64 cores in
> total)
> 
> When I compare it against Mel's patchset
> (git://git.kernel.org/pub/scm/linux/kernel/git/mel/linux.git
> sched-numa-fast-crossnode-v1r12)
> 
>   * Mel's kernel is about 15% faster for stream benchmarks
>   * The other benchmarks show very similar results with both kernels
> 
> Mel's patchset eliminates NUMA migration rate limits, this is
> presumbly the reason for the good stream results.
> 
> Do you have any update when the current patchset could be merged into
> the upstream kernel?
> 

I'm travelling at the moment but when I get back, I'll see what's in the
tip tree with respect to Srikar's patches and then rebase the fast-migration
patches on top and reconfirm they still behave as expected. Assuming
they do, I'll resend them.

  reply	other threads:[~2018-09-17 13:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-07  9:34 Jirka Hladky
2018-09-07 12:56 ` Srikar Dronamraju
2018-09-07 13:19   ` Peter Zijlstra
2018-09-07 13:44     ` Srikar Dronamraju
2018-09-07 13:52       ` Peter Zijlstra
2018-09-09 14:03         ` Jirka Hladky
2018-09-14 14:50           ` Jirka Hladky
2018-09-17 13:06             ` Mel Gorman [this message]
2018-09-17 13:14               ` Jirka Hladky
2018-10-04 13:08 ` Jon Masters

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=20180917130629.nugwsgcsuoda6qf6@techsingularity.net \
    --to=mgorman@techsingularity.net \
    --cc=jhladky@redhat.com \
    --cc=jracek@redhat.com \
    --cc=kkolakow@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=srikar@linux.vnet.ibm.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