From: Mel Gorman <mgorman@techsingularity.net>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Valentin Schneider <valentin.schneider@arm.com>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Aubrey Li <aubrey.li@linux.intel.com>,
Ying Huang <ying.huang@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Mitigate inconsistent NUMA imbalance behaviour
Date: Tue, 31 May 2022 15:09:24 +0100 [thread overview]
Message-ID: <20220531140924.GA3401@techsingularity.net> (raw)
In-Reply-To: <CAKfTPtDnbnNLgE40Xk1r_Hv6J3=wUkLzV15cdmijoVuf9Cy2+A@mail.gmail.com>
On Tue, May 31, 2022 at 12:26:51PM +0200, Vincent Guittot wrote:
> > # cd work/log
> > # ../../compare-kernels.sh
> >
> > nas-mpich-mg NAS Time
> > test
> > mgD-many
> > Min mg.D 95.80 ( 0.00%)
> > Amean mg.D 110.77 ( 0.00%)
> > Stddev mg.D 21.55 ( 0.00%)
> > CoeffVar mg.D 19.46 ( 0.00%)
> > Max mg.D 155.35 ( 0.00%)
> > BAmean-50 mg.D 96.05 ( 0.00%)
> > BAmean-95 mg.D 107.83 ( 0.00%)
> > BAmean-99 mg.D 109.23 ( 0.00%)
> >
> > Note the min of 95.80 seconds, max of 155.35 and high stddev indicating
> > the results are not stable.
> >
> > The generated config is for openSUSE so it may not work for you. After
> > installing the mpich package, you'll need to adjust these lines
> >
> > export NAS_MPICH_PATH=/usr/$MMTESTS_LIBDIR/mpi/gcc/$NAS_MPICH_VERSION/bin
> > export NAS_MPICH_LIBPATH=/usr/$MMTESTS_LIBDIR/mpi/gcc/$NAS_MPICH_VERSION/$MMTESTS_LIBDIR
> >
> > NAS_MPICH_PATH and NAS_MPICH_LIBPATH need to point to the bin and lib
> > path for the mpich package your distribution ships.
>
> I have been able to run your tests on my setup: aarch64 2 nodes * 28
> cores * 4 threads. But I can't reproduce the problem, results stay
> stable before and after reverting c6f886546cb8.
>
It's unfortunate but not surprising that it's not perfectly reproducible
given that I expect this to be a race of some description and not all
machines will observe the problem.
Thanks for trying.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2022-05-31 14:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 10:35 [PATCH v2 0/4] Mitigate inconsistent NUMA imbalance behaviour Mel Gorman
2022-05-20 10:35 ` [PATCH 1/4] sched/numa: Initialise numa_migrate_retry Mel Gorman
2022-06-13 8:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2022-05-20 10:35 ` [PATCH 2/4] sched/numa: Do not swap tasks between nodes when spare capacity is available Mel Gorman
2022-06-13 8:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2022-05-20 10:35 ` [PATCH 3/4] sched/numa: Apply imbalance limitations consistently Mel Gorman
2022-05-27 6:21 ` [sched/numa] 5278ba412f: unixbench.score -2.9% regression kernel test robot
2022-06-13 8:43 ` [tip: sched/core] sched/numa: Apply imbalance limitations consistently tip-bot2 for Mel Gorman
2022-05-20 10:35 ` [PATCH 4/4] sched/numa: Adjust imb_numa_nr to a better approximation of memory channels Mel Gorman
2022-06-13 8:43 ` [tip: sched/core] " tip-bot2 for Mel Gorman
2022-05-24 16:01 ` [PATCH v2 0/4] Mitigate inconsistent NUMA imbalance behaviour Vincent Guittot
2022-05-25 12:49 ` Mel Gorman
2022-05-31 10:26 ` Vincent Guittot
2022-05-31 14:09 ` Mel Gorman [this message]
2022-06-08 9:53 ` K Prateek Nayak
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=20220531140924.GA3401@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=aubrey.li@linux.intel.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=ying.huang@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