From: Valentin Schneider <valentin.schneider@arm.com>
To: lkp@lists.01.org
Subject: Re: [sched/fair] 38ac256d1c: stress-ng.vm-segv.ops_per_sec -13.8% regression
Date: Thu, 22 Apr 2021 10:55:10 +0100 [thread overview]
Message-ID: <87wnsutzi9.mognet@arm.com> (raw)
In-Reply-To: <20210422074742.GE31382@xsang-OptiPlex-9020>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On 22/04/21 15:47, Oliver Sang wrote:
> hi, Valentin Schneider,
>
> On Wed, Apr 21, 2021 at 11:27:49AM +0100, Valentin Schneider wrote:
>> On 21/04/21 11:20, Oliver Sang wrote:
>> > what's the machine model you used upon which the regression cannot be reproduced?
>> > we could check if we have similar model then re-check on the our machine.
>> >
>>
>> I tested this on:
>> o Ampere eMAG (arm64, 32 cores)
>> o 2-socket Xeon E5-2690 (x86, 40 cores)
>>
>> and found at worse a -0.3% regression and at best a 2% improvement. I know
>> that x86 box is somewhat ancient, but it's been my go-to "have I broken
>> x86?" test victim for a while :-)
>
> we don't have exactly 2-socket Xeon E5-2690 model, but we have one:
> Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz (2-socket, 48 cores with 112G memory)
> the test on it shows the regression is existing, too. but smaller (-5.3%)
> hope it's helpful
>
It is, thank you for trying this out on another system and figuring out
it's still visible! I'll go find myself some other x86 box and dig into it;
I'd rather not leave this hanging for too long.
WARNING: multiple messages have this Message-ID (diff)
From: Valentin Schneider <valentin.schneider@arm.com>
To: Oliver Sang <oliver.sang@intel.com>
Cc: 0day robot <lkp@intel.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, ying.huang@intel.com, feng.tang@intel.com,
zhengjun.xing@intel.com,
Lingutla Chandrasekhar <clingutla@codeaurora.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Morten Rasmussen <morten.rasmussen@arm.com>,
Qais Yousef <qais.yousef@arm.com>,
Quentin Perret <qperret@google.com>,
Pavan Kondeti <pkondeti@codeaurora.org>,
Rik van Riel <riel@surriel.com>,
aubrey.li@linux.intel.com, yu.c.chen@intel.com
Subject: Re: [sched/fair] 38ac256d1c: stress-ng.vm-segv.ops_per_sec -13.8% regression
Date: Thu, 22 Apr 2021 10:55:10 +0100 [thread overview]
Message-ID: <87wnsutzi9.mognet@arm.com> (raw)
In-Reply-To: <20210422074742.GE31382@xsang-OptiPlex-9020>
On 22/04/21 15:47, Oliver Sang wrote:
> hi, Valentin Schneider,
>
> On Wed, Apr 21, 2021 at 11:27:49AM +0100, Valentin Schneider wrote:
>> On 21/04/21 11:20, Oliver Sang wrote:
>> > what's the machine model you used upon which the regression cannot be reproduced?
>> > we could check if we have similar model then re-check on the our machine.
>> >
>>
>> I tested this on:
>> o Ampere eMAG (arm64, 32 cores)
>> o 2-socket Xeon E5-2690 (x86, 40 cores)
>>
>> and found at worse a -0.3% regression and at best a 2% improvement. I know
>> that x86 box is somewhat ancient, but it's been my go-to "have I broken
>> x86?" test victim for a while :-)
>
> we don't have exactly 2-socket Xeon E5-2690 model, but we have one:
> Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz (2-socket, 48 cores with 112G memory)
> the test on it shows the regression is existing, too. but smaller (-5.3%)
> hope it's helpful
>
It is, thank you for trying this out on another system and figuring out
it's still visible! I'll go find myself some other x86 box and dig into it;
I'd rather not leave this hanging for too long.
next prev parent reply other threads:[~2021-04-22 9:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 22:06 [PATCH v5 0/3] sched/fair: load-balance vs capacity margins Valentin Schneider
2021-04-07 22:06 ` [PATCH v5 1/3] sched/fair: Ignore percpu threads for imbalance pulls Valentin Schneider
2021-04-09 11:24 ` [tip: sched/core] " tip-bot2 for Lingutla Chandrasekhar
2021-04-09 12:05 ` tip-bot2 for Lingutla Chandrasekhar
2021-04-09 16:14 ` tip-bot2 for Lingutla Chandrasekhar
2021-04-14 5:21 ` [sched/fair] 38ac256d1c: stress-ng.vm-segv.ops_per_sec -13.8% regression kernel test robot
2021-04-14 5:21 ` kernel test robot
2021-04-14 17:17 ` Valentin Schneider
2021-04-14 17:17 ` Valentin Schneider
2021-04-21 3:20 ` Oliver Sang
2021-04-21 3:20 ` Oliver Sang
2021-04-21 10:27 ` Valentin Schneider
2021-04-21 10:27 ` Valentin Schneider
2021-04-21 12:03 ` Peter Zijlstra
2021-04-21 12:03 ` Peter Zijlstra
2021-04-22 7:47 ` Oliver Sang
2021-04-22 7:47 ` Oliver Sang
2021-04-22 9:55 ` Valentin Schneider [this message]
2021-04-22 9:55 ` Valentin Schneider
2021-04-22 20:42 ` Valentin Schneider
2021-04-22 20:42 ` Valentin Schneider
2021-04-28 22:00 ` Valentin Schneider
2021-04-28 22:00 ` Valentin Schneider
2021-05-06 16:11 ` Valentin Schneider
2021-05-06 16:11 ` Valentin Schneider
2021-04-07 22:06 ` [PATCH v5 2/3] sched/fair: Clean up active balance nr_balance_failed trickery Valentin Schneider
2021-04-09 11:24 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2021-04-09 12:05 ` tip-bot2 for Valentin Schneider
2021-04-09 16:14 ` tip-bot2 for Valentin Schneider
2021-04-07 22:06 ` [PATCH v5 3/3] sched/fair: Introduce a CPU capacity comparison helper Valentin Schneider
2021-04-09 11:24 ` [tip: sched/core] " tip-bot2 for Valentin Schneider
2021-04-09 12:05 ` tip-bot2 for Valentin Schneider
2021-04-09 16:14 ` tip-bot2 for Valentin Schneider
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=87wnsutzi9.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=lkp@lists.01.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.