From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Norbert <nbrtt01@gmail.com>, Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Yunfeng Ye <yeyunfeng@huawei.com>,
frederic@kernel.org
Subject: Re: Performance regression: thread wakeup time (latency) increased up to 3x
Date: Fri, 22 Oct 2021 15:03:40 +0200 [thread overview]
Message-ID: <4674203.GXAFRqVoOG@kreacher> (raw)
In-Reply-To: <YW1ZjroFfmKM9HJe@hirez.programming.kicks-ass.net>
On Monday, October 18, 2021 1:25:02 PM CEST Peter Zijlstra wrote:
> On Fri, Oct 15, 2021 at 09:08:58PM -0700, Norbert wrote:
>
> > > > > On Fri, Oct 15, 2021 at 12:43:45AM -0700, Norbert wrote:
> > > > > > Performance regression: thread wakeup time (latency) increased up to 3x.
> > > > > >
> > > > > > Happened between 5.13.8 and 5.14.0. Still happening at least on 5.14.11.
>
> > So git-bisect finally identified the following commit.
> > The performance difference came in a single step. Times were consistent with
> > my first post either the slow time or the fast time,
> > as far as I could tell during the bisection.
> >
> > It is a bit unfortunate that this comes from an attempt to reduce OS noise.
> >
> > -----------------------------------------------------
> > commit a5183862e76fdc25f36b39c2489b816a5c66e2e5
> > Author: Yunfeng Ye <yeyunfeng@huawei.com>
> > Date: Thu May 13 01:29:16 2021 +0200
> >
> > tick/nohz: Conditionally restart tick on idle exit
> >
> > In nohz_full mode, switching from idle to a task will unconditionally
> > issue a tick restart. If the task is alone in the runqueue or is the
> > highest priority, the tick will fire once then eventually stop. But that
> > alone is still undesired noise.
> >
> > Therefore, only restart the tick on idle exit when it's strictly
> > necessary.
> >
> > Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
> > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > Acked-by: Peter Zijlstra <peterz@infradead.org>
> > Link:
> > https://lore.kernel.org/r/20210512232924.150322-3-frederic@kernel.org
> > -----------------------------------------------------
> >
> > Is there anything else to do to complete this report?
>
> So it _could_ be you're seeing increased use of deeper idle states due
> to less noise. I'm forever forgetting what the most friendly tool is for
> checking that (powertop can I think), Rafael?
You can use turbostat too.
> One thing to try is boot with idle=halt and see if that makes a
> different.
>
> Also, let me Cc all the people involved.. the thread starts:
>
> https://lkml.kernel.org/r/035c23b4-118e-6a35-36d9-1b11e3d679f8@gmail.com
>
next prev parent reply other threads:[~2021-10-22 13:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 7:43 Performance regression: thread wakeup time (latency) increased up to 3x Norbert
2021-10-15 8:52 ` Peter Zijlstra
2021-10-15 9:36 ` Norbert
2021-10-15 14:04 ` Steven Rostedt
2021-10-16 4:08 ` Norbert
2021-10-18 11:25 ` Peter Zijlstra
2021-10-19 1:56 ` Norbert
2021-10-19 7:01 ` Norbert
2021-11-07 15:56 ` Frederic Weisbecker
2021-11-08 15:56 ` Norbert
2021-10-22 13:03 ` Rafael J. Wysocki [this message]
2021-10-24 5:09 ` Norbert
2021-11-02 1:35 ` Norbert
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=4674203.GXAFRqVoOG@kreacher \
--to=rjw@rjwysocki.net \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nbrtt01@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=yeyunfeng@huawei.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