From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Chris Mason <clm@meta.com>, Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
vschneid@redhat.com, Juri Lelli <juri.lelli@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: scheduler performance regression since v6.11
Date: Wed, 21 May 2025 15:59:29 +0200 [thread overview]
Message-ID: <d1002060-a1e4-4c47-aeb4-d8af0744267a@arm.com> (raw)
In-Reply-To: <23576497-af63-4074-8724-d75d0dca1817@meta.com>
On 20/05/2025 16:53, Chris Mason wrote:
> On 5/20/25 10:38 AM, Dietmar Eggemann wrote:
>> On 16/05/2025 12:18, Peter Zijlstra wrote:
>>> On Mon, May 12, 2025 at 06:35:24PM -0400, Chris Mason wrote:
[...]
>> I can't spot any v6.11 related changes (dl_server or TTWU_QUEUE) but a
>> PSI related one for v6.12 results in a ~8% schbench regression.
>>
>> VM (m7gd.16xlarge, 16 logical CPUs) on Graviton3:
>>
>> schbench -L -m 4 -M auto -t 128 -n 0 -r 60
>>
>> 3840cbe24cf0 - sched: psi: fix bogus pressure spikes from aggregation race
>
> I also saw a regression on this one, but it wasn't stable enough for me
> to be sure. I'll retest, but I'm guessing this is made worse by the VM
> / graviton setup?
For me the 8% regression here is pretty stable. I have to add that I ran
schbench in:
/sys/fs/cgroup/user.slice/user-1000.slice/session-33.scope
So that explains IMHO the 4 calls to psi_group_change() from
psi_task_switch() now doing all their own 'now = cpu_clock(cpu)' call.
schbench-6509 [004] d.... 689.050466: psi_task_switch: CPU4 [schbench 6509] -> [schbench 6514] ->
schbench-6509 [004] d.... 689.050466: psi_group_change: CPU4 now=689050466118
schbench-6509 [004] d.... 689.050467: psi_group_change: CPU4 now=689050466537
schbench-6509 [004] d.... 689.050467: psi_group_change: CPU4 now=689050466950
schbench-6509 [004] d.... 689.050468: psi_group_change: CPU4 now=689050467838
schbench-6509 [004] d.... 689.050468: psi_task_switch: CPU4 [schbench 6509] -> [schbench 6514] <-
> I've been testing Peter's changes, and they do help on my skylake box
> but not as much on the big turin machines. I'm trying to sort that out,
Turin vs. SKL,SPR ?
> but we have some other variables wrt PGO/LTO that I need to rule out.
OK, thanks! We also started testing this on Arm64 server with +20 cores ...
[...]
next prev parent reply other threads:[~2025-05-21 13:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 23:13 Chris Mason
2025-05-09 19:49 ` Peter Zijlstra
2025-05-12 18:08 ` Peter Zijlstra
2025-05-12 19:39 ` Chris Mason
2025-05-12 22:35 ` Chris Mason
2025-05-13 7:15 ` Peter Zijlstra
2025-05-16 10:18 ` Peter Zijlstra
2025-05-20 14:38 ` Dietmar Eggemann
2025-05-20 14:53 ` Chris Mason
2025-05-21 13:59 ` Dietmar Eggemann [this message]
2025-05-21 14:32 ` Chris Mason
2025-05-20 19:38 ` Peter Zijlstra
2025-05-21 14:02 ` Dietmar Eggemann
2025-05-21 15:02 ` Peter Zijlstra
2025-05-21 19:00 ` Peter Zijlstra
2025-05-21 14:54 ` Peter Zijlstra
2025-05-22 8:48 ` Peter Zijlstra
2025-05-22 15:00 ` Johannes Weiner
2025-05-23 15:40 ` Peter Zijlstra
2025-05-23 12:27 ` Dietmar Eggemann
2025-07-10 12:46 ` [tip: sched/core] sched/psi: Optimize psi_group_change() cpu_clock() usage tip-bot2 for Peter Zijlstra
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=d1002060-a1e4-4c47-aeb4-d8af0744267a@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=clm@meta.com \
--cc=juri.lelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®