Bug#911815: /usr/bin/perf_4.18: Please build perf against libbfd
Package: linux-perf-4.18
Version: 4.18.10-2
Severity: wishlist
File: /usr/bin/perf_4.18
Dear Maintainer,
Running e.g. perf report with dwarf call graph info can take a long time
depending on the size of the profile and the size of dwarf info in the
binaries being profiled. That's because each address in each library is
handled by forking and executing a new addr2line process. Each addr2line
process has to parse the dwarf info of the library it's given just to
find the location of one address. Multiply by the number of addresses,
and this can quickly become ridiculous.
Perf, however, has an alternative implementation that just uses libbfd,
so it would be much faster than spawning a large amount of new
processes, each with a large overhead.
Mike
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-perf-4.18 depends on:
ii libbabeltrace1 1.5.6-1
ii libc6 2.27-6
ii libdw1 0.170-0.5
ii libelf1 0.170-0.5
ii liblzma5 5.2.2-1.3
ii libnuma1 2.0.12-1
ii libperl5.26 5.26.2-7+b1
ii libpython3.6 3.6.7-1
ii libslang2 2.3.2-1+b1
ii libunwind8 1.2.1-8
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages linux-perf-4.18 recommends:
ii linux-base 4.5
Versions of packages linux-perf-4.18 suggests:
pn linux-doc-4.18 <none>
-- no debconf information
Reply to: