From: Josef Bacik <josef@toxicpanda.com>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: peterz@infradead.org, vincent.guittot@linaro.org,
torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [REGRESSION] 5-10% increase in IO latencies with nohz balance patch
Date: Mon, 29 Nov 2021 14:49:28 -0500 [thread overview]
Message-ID: <YaUuyN3h07xlEx8j@localhost.localdomain> (raw)
In-Reply-To: <87bl22byq2.mognet@arm.com>
On Mon, Nov 29, 2021 at 06:31:17PM +0000, Valentin Schneider wrote:
> On 29/11/21 13:15, Josef Bacik wrote:
> > On Mon, Nov 29, 2021 at 06:03:24PM +0000, Valentin Schneider wrote:
> >> Would you happen to have execution traces by any chance? If not I should be
> >> able to get one out of that fsperf thingie.
> >>
> >
> > I don't, if you want to tell me how I can do it right now. I've disabled
> > everything on this box for now so it's literally just sitting there waiting to
> > have things done to it. Thanks,
> >
>
> I see you have Ftrace enabled in your config, so that ought to do it:
>
> trace-cmd record -e 'sched:*' -e 'cpu_idle' $your_test_cmd
>
http://toxicpanda.com/performance/trace.dat
it's like 16mib. Enjoy,
Josef
next prev parent reply other threads:[~2021-11-29 22:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 17:03 [REGRESSION] 5-10% increase in IO latencies with nohz balance patch Josef Bacik
2021-11-29 18:03 ` Valentin Schneider
2021-11-29 18:15 ` Josef Bacik
2021-11-29 18:31 ` Valentin Schneider
2021-11-29 19:49 ` Josef Bacik [this message]
2021-11-30 0:26 ` Valentin Schneider
2021-12-03 12:03 ` Valentin Schneider
2021-12-03 19:00 ` Josef Bacik
2021-12-06 9:48 ` Valentin Schneider
2021-12-09 17:22 ` Valentin Schneider
2021-12-09 19:16 ` Josef Bacik
2021-12-22 12:42 ` Thorsten Leemhuis
2021-12-22 16:07 ` Valentin Schneider
2022-01-03 16:16 ` Josef Bacik
2022-01-13 16:41 ` Valentin Schneider
2022-01-13 16:57 ` Roman Gushchin
2022-02-18 11:00 ` Thorsten Leemhuis
2022-02-18 15:34 ` Josef Bacik
2021-11-30 7:16 ` Thorsten Leemhuis
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=YaUuyN3h07xlEx8j@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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;
as well as URLs for NNTP newsgroup(s).