Re: Performance regression: thread wakeup time (latency) increased up to 3x

[Norbert]

On 10/15/21 07:04, Steven Rostedt wrote:
> On Fri, 15 Oct 2021 02:36:03 -0700
> Norbert <nbrtt01@xxxxxxxxx> wrote:
>
> > On 10/15/21 01:52, Peter Zijlstra 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.
> > >
> > > Could you git-bisect this?
> > >    
> >
> > So far I haven't built a kernel yet, I'm quite new to Linux in that way,
> > so it may take me some time to figure it all out, but yes.
>
> If you do test a kernel you build yourself, you may want to use
> "localmodconfig". Which will look at all the modules that are loaded on the
> local system and turn off the configs for modules that are not loaded. This
> will save a lot of time compiling the kernel. Especially if your basing off
> of a distro config.
>
>    $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>    $ cd linux
>    $ cp /boot/config-[whatever your kernel is] .config
>    $ yes '' | make localmodconfig
>
> Then build your kernel.
>
>    $ make -j10
>    $ sudo make modules_install install
>
> > (By the way, of course I meant that throughput *de*creases, not increases.)
>
> of course ;-)
>
> -- Steve

Thank you, localmodconfig is an enormous timesaver. Once I got some 
local build problems/modules out of the way, this method worked very well.

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@xxxxxxxxxx>
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@xxxxxxxxxx>
    Signed-off-by: Frederic Weisbecker <frederic@xxxxxxxxxx>
    Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx>
    Acked-by: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
    Link: 
https://lore.kernel.org/r/20210512232924.150322-3-frederic@xxxxxxxxxx
-----------------------------------------------------

Is there anything else to do to complete this report?