From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCHSET v3 0/3] perf tools: Minor improvements in event synthesis
Date: Tue, 2 Feb 2021 13:40:07 +0100 [thread overview]
Message-ID: <YBlIJzIZ1nEesWS9@krava> (raw)
In-Reply-To: <20210202090118.2008551-1-namhyung@kernel.org>
On Tue, Feb 02, 2021 at 06:01:15PM +0900, Namhyung Kim wrote:
> Hello,
>
> This is to optimize the event synthesis during perf record.
>
> Changes in v3:
> * remove unnecessary pid check
> * update change log in patch #2
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
>
> The first patch is to reduce memory usage when many threads are used.
> The second is to avoid unncessary syscalls for kernel threads. And
> the last one is to reduce the number of threads to iterate when new
> threads are being created at the same time.
>
> Unfortunately there's no dramatic improvement here but I can see ~5%
> gain in the 'perf bench internals synthesize' on a big machine.
> (The numbers are not stable though)
>
>
> Before:
> # perf bench internals synthesize --mt -M1 -I 100
> # Running 'internals/synthesize' benchmark:
> Computing performance of multi threaded perf event synthesis by
> synthesizing events on CPU 0:
> Number of synthesis threads: 1
> Average synthesis took: 68831.480 usec (+- 101.450 usec)
> Average num. events: 9982.000 (+- 0.000)
> Average time per event 6.896 usec
>
>
> After:
> # perf bench internals synthesize --mt -M1 -I 100
> # Running 'internals/synthesize' benchmark:
> Computing performance of multi threaded perf event synthesis by
> synthesizing events on CPU 0:
> Number of synthesis threads: 1
> Average synthesis took: 65036.370 usec (+- 158.121 usec)
> Average num. events: 9982.000 (+- 0.000)
> Average time per event 6.515 usec
>
>
> Thanks,
> Namhyung
>
>
> Namhyung Kim (3):
> perf tools: Use /proc/<PID>/task/<TID>/status for synthesis
> perf tools: Skip MMAP record synthesis for kernel threads
> perf tools: Use scandir() to iterate threads
>
> tools/perf/util/synthetic-events.c | 83 +++++++++++++++++++-----------
> 1 file changed, 53 insertions(+), 30 deletions(-)
>
> --
> 2.30.0.365.g02bc693789-goog
>
next prev parent reply other threads:[~2021-02-02 12:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 9:01 [PATCHSET v3 0/3] perf tools: Minor improvements in event synthesis Namhyung Kim
2021-02-02 9:01 ` [PATCH 1/3] perf tools: Use /proc/<PID>/task/<TID>/status for synthesis Namhyung Kim
2021-02-02 9:01 ` [PATCH 2/3] perf tools: Skip MMAP record synthesis for kernel threads Namhyung Kim
2021-02-02 9:01 ` [PATCH 3/3] perf tools: Use scandir() to iterate threads Namhyung Kim
2021-02-02 12:40 ` Jiri Olsa [this message]
2021-02-03 13:09 ` [PATCHSET v3 0/3] perf tools: Minor improvements in event synthesis Arnaldo Carvalho de Melo
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=YBlIJzIZ1nEesWS9@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--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