mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Linus Torvalds' <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Linux 6.10-rc2 - massive performance regression
Date: Sat, 8 Jun 2024 21:35:48 +0000	[thread overview]
Message-ID: <adbbd899aabf4e6898bbbb04f90b3ede@AcuMS.aculab.com> (raw)
In-Reply-To: <CAHk-=wh170Lme6HHSGa5eM6YNcd01vdkOoPenZ0m7P+Yv6_zxg@mail.gmail.com>

From: Linus Torvalds
> Sent: 08 June 2024 17:03
> 
> On Sat, 8 Jun 2024 at 07:44, David Laight <David.Laight@aculab.com> wrote:
> >
> > I suspect it is due to the changes to the way the scheduler pre-empts
> > processes.
> 
> The PREEMPT_AUTO changes haven't even made it into the kernel yet,
> only a couple of preliminary rcu patches that aren't relevant yet.
> 
> So while there's been some scheduler changes in 6.10, they have mostly
> been pretty insignificant - mostly some renaming without functional
> changes, and one-liners.
> 
> Obviously even a one-liner can end up resulting in random oddities,
> but could you try to bisect the issue you see to pin it down?

I'll try to remember how to bisect through the merge :-)

I've done some tests.
I'm seeing a three-fold slow down on:
$ i=0; while [ $i -lt 1000000 ]; do i=$((i + 1)); done
which goes from 1 second to 3.

I can run that with ftrace monitoring scheduler events (and a few
other things) and can't spot anywhere the process isn't running
for a significant time.

I've just had a thought.
Have there been any changes to the code that changes the cpu speed
and/or scheduler decisions for migrating processes?

It might be that the busy single process keeps on being migrated
to an idle cpu that is running at 800MHz rather than staying on
a cpu and getting its speed ramped up to 3.5-4GHz

I can speed the shell loop up to just over 2 seconds by running
a few copies of:
$ while :; do :; done
That might be the best I can get since I'm using an i7-7700 (4 cores
with hyperthreading giving 8 cpu) and hyperthreading probably slows
things down by a factor of two.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2024-06-08 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02 22:50 Linux 6.10-rc2 Linus Torvalds
2024-06-03  7:03 ` Build regressions/improvements in v6.10-rc2 Geert Uytterhoeven
2024-06-08 14:44 ` Linux 6.10-rc2 - massive performance regression David Laight
2024-06-08 16:02   ` Linus Torvalds
2024-06-08 21:35     ` David Laight [this message]
2024-06-08 22:00       ` Linus Torvalds
2024-06-08 22:28         ` Woody Suwalski
2024-06-09  8:07         ` Johan Hovold
2024-06-09  8:11         ` Linux regression tracking (Thorsten Leemhuis)
2024-06-09  9:35           ` David Laight
2024-06-09 14:24         ` David Laight

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=adbbd899aabf4e6898bbbb04f90b3ede@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 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®