Your message dated Wed, 11 Jun 2025 18:14:16 +0200
with message-id <[email protected]>
and subject line Re: Bug#1088153: linux-perf: "perf script" is extremely slow
has caused the Debian Bug report #1088153,
regarding linux-perf: "perf script" is extremely slow
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1088153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088153
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-perf
Version: 6.11.9-1
Severity: normal
Dear Maintainer,
I am trying to use cargo-flamegraph to produce a flamegraph from perf data. That
invokes "perf script" and that has now been running already 15 minutes on a tiny
perf file containing 3300 samples. Something is extremely slow here, making some
kinds of perf analysis basically impossible.
Looking around for perf performance issues, I found
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815, which however is
supposed to have been fixed years ago. But I still see thousands and thousands
of addr2line processes being spawned, so somehow
<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be8ecc57f180415e8a7c1cc5620c5236be2a7e56>
either did not have the desired effect or is not present in current kernels any
more?
When I finally killed "perf script", I saw a lot of this kind of output:
addr2line
/home/r/.debug/.build-id/37/8f73d84f9d89f55dfc18a9ab84bce321cd9b09/elf: could
not read first record
I don't know whether that could cause the slowdown, or what could cause that
error.
Kind regards,
Ralf
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.11.4-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-perf depends on:
ii libbabeltrace1 1.5.11-4
ii libc6 2.40-3
ii libcap2 1:2.66-5+b1
ii libdebuginfod1t64 0.192-4
ii libdw1t64 0.192-4
ii libelf1t64 0.192-4
ii liblzma5 5.6.3-1+b1
ii libnuma1 2.0.18-1+b1
ii libopencsd1 1.5.2-1+b1
ii libperl5.40 5.40.0-6
ii libpython3.12t64 3.12.7-3
ii libslang2 2.3.3-5+b1
ii libstdc++6 14.2.0-6
ii libtraceevent1 1:1.8.4-1
ii libunwind8 1.6.2-3.1
ii libzstd1 1.5.6+dfsg-1+b1
ii perl 5.40.0-6
ii python3 3.12.6-1
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
linux-perf recommends no packages.
Versions of packages linux-perf suggests:
pn linux-doc-6.11 <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Ralf,
On Wed, Jun 11, 2025 at 04:45:21PM +0200, Ralf Jung wrote:
> Hi,
>
> > On Sun, Nov 24, 2024 at 10:45:50AM +0100, Ralf Jung wrote:
> > > Package: linux-perf
> > > Version: 6.11.9-1
> > > Severity: normal
> > >
> > > Dear Maintainer,
> > >
> > > I am trying to use cargo-flamegraph to produce a flamegraph from perf
> > > data. That
> > > invokes "perf script" and that has now been running already 15 minutes on
> > > a tiny
> > > perf file containing 3300 samples. Something is extremely slow here,
> > > making some
> > > kinds of perf analysis basically impossible.
> > >
> > > Looking around for perf performance issues, I found
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911815, which however is
> > > supposed to have been fixed years ago. But I still see thousands and
> > > thousands
> > > of addr2line processes being spawned, so somehow
> > > <https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=be8ecc57f180415e8a7c1cc5620c5236be2a7e56>
> > > either did not have the desired effect or is not present in current
> > > kernels any
> > > more?
> > >
> > > When I finally killed "perf script", I saw a lot of this kind of output:
> > >
> > > addr2line
> > > /home/r/.debug/.build-id/37/8f73d84f9d89f55dfc18a9ab84bce321cd9b09/elf:
> > > could not read first record
> > >
> > > I don't know whether that could cause the slowdown, or what could cause
> > > that error.
> >
> > Is this still something you can reproduce?
>
> On a quick check, it seems like "perf script" now finishes in a few seconds
> now.
Ack, thank you for quickly reporting back. In this case let's close
the bug.
Regards,
Salvatore
--- End Message ---
