mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jan-Oliver Kaiser <janno@mpi-sws.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, milian.wolff@kdab.com
Subject: Re: `perf report` about 1000x(!) slower in linux 4.15
Date: Tue, 20 Mar 2018 10:38:51 -0300	[thread overview]
Message-ID: <20180320133851.GB3784@kernel.org> (raw)
In-Reply-To: <c6aa77d0-3d0c-bd03-aaa9-f1c33eff277f@mpi-sws.org>

Em Tue, Mar 20, 2018 at 12:57:29PM +0100, Jan-Oliver Kaiser escreveu:
> After upgrading my system to linux 4.15 (from 4.14), `perf report` became
> unusably slow. I estimate a decrease in performance by a factor of
> 100x-1000x. Some 21M perf.data files take about 30 seconds in the
> "Processing events" step.  `git bisect` points to
 
> commit d8a88dd243a170a226aba33e7c53704db2f82aa6 (HEAD, refs/bisect/bad)
> Author: Milian Wolff <milian.wolff@kdab.com>
>     perf util: Enable handling of inlined frames by default
 
> The slowdown can be worked around with `--no-inline`. If the slowdown is
> expected, I would suggest reverting the default setting here or maybe
> printing a warning if a lot of time is spent on this feature.
 
> Do you need any additional information about my system or the recorded data
> I am looking at?

Can you try with the latest perf tool? 

[acme@jouet perf]$ make perf-tarxz-src-pkg ; ls -la perf-4*
  TAR
  PERF_VERSION = 4.16.rc6.gecd380
-rw-rw-r--. 1 acme acme 1323568 Mar 20 10:30 perf-4.16.0-rc6.tar.xz
[acme@jouet perf]$

With a recently checked out kernel sources, or, as a convenience, I'm
pushing this to:

  http://vger.kernel.org/~acme/perf/perf-4.16.0-rc6.tar.xz

You just expand it and then:

[acme@jouet tmp]$ tar xf perf-4.16.0-rc6.tar.xz 
[acme@jouet tmp]$ cd perf-4.16.0-rc6/
[acme@jouet perf-4.16.0-rc6]$ make -C tools/perf install-bin


And check if the problem is present there as well.

If it is, please tell us what is your distro, the output of:

perf report --header-only

Thanks,

- Arnaldo

  reply	other threads:[~2018-03-20 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 11:57 Jan-Oliver Kaiser
2018-03-20 13:38 ` Arnaldo Carvalho de Melo [this message]
2018-03-20 16:54   ` Jan-Oliver Kaiser

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=20180320133851.GB3784@kernel.org \
    --to=acme@kernel.org \
    --cc=janno@mpi-sws.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=milian.wolff@kdab.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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

Powered by JetHome