From: James Clark <james.clark@linaro.org>
To: Thomas Richter <tmricht@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org, namhyung@kernel.org
Cc: agordeev@linux.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH] perf/test: Speed up test case perf annotate basic tests
Date: Tue, 17 Sep 2024 13:52:21 +0100 [thread overview]
Message-ID: <59c2cbb8-b24d-429f-b4fc-6a2560ce4e09@linaro.org> (raw)
In-Reply-To: <20240917085706.249691-1-tmricht@linux.ibm.com>
On 17/09/2024 09:57, Thomas Richter wrote:
> perf test 70 takes a long time. One culprit is the output of command
> perf annotate. Per default enabled are
> - demangle symbol names
> - interleave source code with assembly code.
> Disable demangle of symbols and abort the annotation
> after the first 250 lines.
>
> This speeds up the test case considerable, for example
> on s390:
>
> Output before:
> # time perf test 70
> 70: perf annotate basic tests : Ok
> .....
> real 2m7.467s
> user 1m26.869s
> sys 0m34.086s
> #
>
> Output after:
> # time perf test 70
> 70: perf annotate basic tests : Ok
>
> real 0m3.341s
> user 0m1.606s
> sys 0m0.362s
> #
>
Interesting that there is such a big difference, I only measured 4s vs
14s without the patch.
Either way it's slightly faster now:
Reviewed-by: James Clark <james.clark@linaro.org>
next prev parent reply other threads:[~2024-09-17 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 8:57 [PATCH] perf/test: Speed up test case perf annotate basic tests Thomas Richter
2024-09-17 12:51 ` James Clark
2024-09-17 12:52 ` James Clark [this message]
2024-09-27 17:01 ` Namhyung Kim
-- strict thread matches above, loose matches on Subject: below --
2024-06-13 11:26 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=59c2cbb8-b24d-429f-b4fc-6a2560ce4e09@linaro.org \
--to=james.clark@linaro.org \
--cc=acme@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.com \
/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).