From: Thomas Richter <tmricht@linux.ibm.com>
To: "linux-perf-use." <linux-perf-users@vger.kernel.org>
Cc: Jan Polensky <japo@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: [linux-next] perf report runtime extremely long
Date: Wed, 29 Oct 2025 09:03:13 +0100 [thread overview]
Message-ID: <09943f4f-516c-4b93-877c-e4a64ed61d38@linux.ibm.com> (raw)
Hi all,
has something changed recently in perf report in linux-next repo?
I run perf report -i <file> -D | grep something
on s390 with 2 different kernels:
master 6.18.0rc3:
# uname -a
Linux a35lp67.lnxne.boe 6.18.0-rc3m-perf+ #23 SMP Tue Oct 28 15:53:44 CET 2025 s390x GNU/Linux
# ll /tmp/perf2-eSso2q-2
-rw------- 1 root root 8538184 Oct 29 08:44 /tmp/perf2-eSso2q-2
# time perf report -i/tmp/perf2-eSso2q-2 -D | grep Counter:000 > /dev/null
real 0m22.262s
user 0m22.068s
sys 0m0.200s
#
This runtime is ok for the perf.data file size.
linux-next:
# uname -a
Linux s83lp47.lnxne.boe 6.18.0-20251028.rc3.git141.f7d2388eeec2.63.fc42.s390x+next #1 SMP Tue Oct 28 20:06:13 CET 2025 s390x GNU/Linux
#ll /tmp/perf2-eSso2q-2
-rw-------. 1 root root 8538184 Oct 29 08:47 /tmp/perf2-eSso2q-2
# time perf report -i/tmp/perf2-eSso2q-2 -D | grep Counter:000 > /dev/null
real 2m53.601s
user 2m52.938s
sys 0m0.575s
#
Same perf.data file and run time increased from 22 seconds to nearly 300 seconds, roughly 14 times longer
for the same input!
Has anybody similar observations?
Thanks a lot
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2025-10-29 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 8:03 Thomas Richter [this message]
2025-10-29 15:13 ` [linux-next] perf report runtime extremely long Ian Rogers
2025-10-29 15:52 ` Thomas Richter
2025-10-29 16:25 ` Ian Rogers
2025-10-29 15:56 ` Thomas Richter
2025-10-29 16:47 ` Ian Rogers
2025-10-30 6:04 ` Namhyung Kim
2025-10-30 8:59 ` Thomas Richter
2025-10-30 13:25 ` Thomas Richter
2025-10-30 14:27 ` Thomas Richter
2025-10-30 15:57 ` Ian Rogers
2025-10-30 17:14 ` Ian Rogers
2025-10-31 8:20 ` Thomas Richter
2025-10-31 7:06 ` Thomas Richter
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=09943f4f-516c-4b93-877c-e4a64ed61d38@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=japo@linux.ibm.com \
--cc=linux-perf-users@vger.kernel.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).