From: Joseph Salisbury <joseph.salisbury@oracle.com>
To: clm@fb.com
Cc: Peter Zijlstra <peterz@infradead.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Juri Lelli <juri.lelli@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
dietmar.eggemann@arm.com, Steven Rostedt <rostedt@goodmis.org>,
bsegall@google.com, mgorman@suse.de, vschneid@redhat.com,
LKML <linux-kernel@vger.kernel.org>
Subject: [REGRESSION][v6.17-rc1]sched/fair: Bump sd->max_newidle_lb_cost when newidle balance fails
Date: Mon, 6 Oct 2025 16:23:19 -0400 [thread overview]
Message-ID: <006c9df2-b691-47f1-82e6-e233c3f91faf@oracle.com> (raw)
Hi Chris,
During testing, we are seeing a ~6% performance regression with the
upstream stable v6.12.43 kernel (And Oracle UEK
6.12.0-104.43.4.el9uek.x86_64 kernel) when running the Phoronix
pts/apache benchmark with 100 concurrent requests [0]. The regression
is seen with the following hardware:
PROCESSOR: Intel Xeon Platinum 8167M Core Count: 8 Thread Count: 16
Extensions: SSE 4.2 + AVX512CD + AVX2 + AVX + RDRAND + FSGSBASE Cache
Size: 16 MB Microcode: 0x1 Core Family: Cascade Lake
After performing a bisect, we found that the performance regression was
introduced by the following commit:
Stable v6.12.43: fc4289233e4b ("sched/fair: Bump sd->max_newidle_lb_cost
when newidle balance fails")
Mainline v6.17-rc1: 155213a2aed4 ("sched/fair: Bump
sd->max_newidle_lb_cost when newidle balance fails")
Reverting this commit causes the performance regression to not exist.
I was hoping to get your feedback, since you are the patch author. Do
you think gathering any additional data will help diagnose this issue?
Thanks,
Joe
[0]https://openbenchmarking.org/test/pts/apache-3.0.0
next reply other threads:[~2025-10-06 20:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 20:23 Joseph Salisbury [this message]
2025-10-06 21:23 ` [REGRESSION][v6.17-rc1]sched/fair: Bump sd->max_newidle_lb_cost when newidle balance fails Chris Mason
2025-10-07 11:34 ` Peter Zijlstra
2025-10-10 1:04 ` [External] : " Joseph Salisbury
2025-10-10 17:09 ` Peter Zijlstra
2025-10-17 17:01 ` Joseph Salisbury
2025-10-30 7:29 ` Adam Li
2025-10-31 21:16 ` [External] : " Joseph Salisbury
2025-11-04 18:11 ` Joseph Salisbury
2025-10-30 7:22 ` Adam Li
2025-10-30 9:30 ` Peter Zijlstra
2025-10-30 20:53 ` Dietmar Eggemann
2025-10-31 2:46 ` Adam Li
2025-10-10 1:14 ` Joseph Salisbury
2025-10-07 20:22 ` [External] : " Joseph Salisbury
2025-10-10 13:09 ` Hazem Mohamed Abuelfotoh
2025-10-27 18:36 ` Josh Don
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=006c9df2-b691-47f1-82e6-e233c3f91faf@oracle.com \
--to=joseph.salisbury@oracle.com \
--cc=bsegall@google.com \
--cc=clm@fb.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--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