All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Jirka Hladky <jhladky@redhat.com>,
	Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-kernel@vger.kernel.org, mgorman@suse.de, peterz@infradead.org
Subject: Re: [PATCH] numa,sched: only consider less busy nodes as numa balancing destination
Date: Mon, 11 May 2015 10:44:00 -0400	[thread overview]
Message-ID: <5550C030.8040001@redhat.com> (raw)
In-Reply-To: <5550A446.2050005@redhat.com>

On 05/11/2015 08:44 AM, Jirka Hladky wrote:
> Hi Rik,
> 
> we have results for SPECjbb2005 and Linpack&Stream benchmarks with
> 
> 4.1.0-0.rc1.git0.1.el7.x86_64 (without patch)
> 4.1.0-0.rc2.git0.3.el7.x86_64 with your patch
> 4.1.0-0.rc2.git0.3.el7.x86_64 with your patch and AUTONUMA disabled
> 
> The tests has been conducted on 3 different systems with 4 NUMA nodes
> and different versions of Intel processors and different amount of RAM.
> 
> 
> For SPECjbb benchmark we see
> -with your latest proposed patch applied
>   * gains in range 7-15% !! for single instance  SPECjbb (tested on
> variety of systems, biggest gains on brickland system, gains are growing
> with growing number of threads)

That is significant.

>   * for multi-instance SPECjbb run (4 parallel jobs on 4 NUMA node
> system) on change in results
>   * for linpack no change
>   * for stream bench slight improvements (but very close to error margin)

Glad to hear the patch is not causing regressions.

Peter, can you queue up this patch in your sched tree, or
would you like me to make any changes to it first?

-- 
All rights reversed

  reply	other threads:[~2015-05-11 14:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 10:35 autoNUMA web workload regression Artem Bityutskiy
2015-05-06 10:37 ` Bityutskiy, Artem
2015-05-06 14:40 ` Rik van Riel
2015-05-06 15:41 ` [PATCH] numa,sched: only consider less busy nodes as numa balancing destination Rik van Riel
2015-05-06 17:00   ` Peter Zijlstra
2015-05-06 17:06     ` Rik van Riel
2015-05-07 13:29   ` Artem Bityutskiy
2015-05-08 13:13   ` Artem Bityutskiy
2015-05-08 20:03     ` Rik van Riel
2015-05-08 22:52       ` Rik van Riel
2015-05-11 11:11       ` Artem Bityutskiy
2015-05-11 14:20         ` Rik van Riel
2015-05-12 13:50       ` Artem Bityutskiy
2015-05-12 15:45         ` Rik van Riel
2015-05-13  6:29           ` Peter Zijlstra
2015-05-13  6:31             ` Peter Zijlstra
2015-05-13 10:59             ` Artem Bityutskiy
2015-05-13 13:51             ` Rik van Riel
2015-05-11 12:44   ` Jirka Hladky
2015-05-11 14:44     ` Rik van Riel [this message]
2015-05-26 20:29   ` Rik van Riel

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=5550C030.8040001@redhat.com \
    --to=riel@redhat.com \
    --cc=dedekind1@gmail.com \
    --cc=jhladky@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.