[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cizPC3p0-Z1oYsDPofwNfZHyKYiJR5JXEcS31Q=mgzcLg@mail.gmail.com>
Date: Tue, 6 Dec 2022 10:32:35 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Petar Gligoric <petar.gligor@...il.com>
Cc: linux-kernel@...r.kernel.org,
Petar Gligoric <petar.gligoric@...de-schwarz.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Andi Kleen <ak@...ux.intel.com>, Jiri Olsa <jolsa@...nel.org>,
Ian Rogers <irogers@...gle.com>
Subject: Re: [PATCH v2 0/3] perf: introduce perf based task analyzer
Hello,
On Tue, Dec 6, 2022 at 7:44 AM Petar Gligoric <petar.gligor@...il.com> wrote:
>
> From: Petar Gligoric <petar.gligoric@...de-schwarz.com>
>
> This patch-series introduces the task analyzer and adds the feature to
> output csv files for further analysis in thirds party script
> (e.g. pandas and friends).
>
> The task analyzer dissects recorded perf.data files based on
> sched:sched_switch events. It outputs useful information for the user
> of each task, like times between schedule in/schedule out of the same
> task.
>
> Switched-In Switched-Out CPU PID TID Comm Runtime Time Out-In
> 15576.658891407 15576.659156086 4 2412 2428 gdbus 265 1949
> 15576.659111320 15576.659455410 0 2412 2412 gnome-shell 344 2267
> 15576.659491326 15576.659506173 2 74 74 kworker/2:1 15 13145
> [...]
>
> The user can modify the output to his liking and his necessity. He can
> either limit the output to tasks he wants or filter tasks he does not
> present in the output. The output can also be limited via the time or
> specific tasks can be highlight via colors. A combination of those
> options is also possible.
> Additionally the user can print out a summary of all tasks, which is a
> table of information from all tasks throughout the whole trace.
> Information, like total runtime, how many times the tasks have been
> scheduled in, what the max runtime was and when it occurred, just to
> name few.
>
> Summary
> Task Information Runtime Information
> PID TID Comm Runs Accumulated Mean Median Min Max Max At
> 14 14 ksoftirqd/0 13 334 26 15 9 127 15571.621211956
> 15 15 rcu_preempt 133 1778 13 13 2 33 15572.581176024
> 16 16 migration/0 3 49 16 13 12 24 15571.608915425
> [...]
>
> The standard task as well as the summary can be printed in either
> nanoseconds, milliseconds or microseconds(standard).
> Both standard as well as summary can be saved in a user specified file
> in csv format.
Have you looked at 'perf sched timehist' ?
I think it has the common functionality and can be easily extended if there's
missing one.
Thanks,
Namhyung
>
> v2:
> - Add tests for new perf task-analyzer suggested by Ian Rogers
>
> Hagen Paul Pfeifer (1):
> perf script: introduce task analyzer
>
> Petar Gligoric (2):
> perf script: task-analyzer add csv support
> perf test: Add new task-analyzer tests
>
> Cc: Arnaldo Carvalho de Melo <acme@...hat.com>
> Cc: Andi Kleen <ak@...ux.intel.com>
> Cc: Jiri Olsa <jolsa@...nel.org>
> Cc: Ian Rogers <irogers@...gle.com>
> Cc: Namhyung Kim <namhyung@...nel.org>
>
> .../scripts/python/bin/tasks-analyzer-record | 2 +
> .../scripts/python/bin/tasks-analyzer-report | 3 +
> tools/perf/scripts/python/tasks-analyzer.py | 937 ++++++++++++++++++
> 3 files changed, 942 insertions(+)
> create mode 100755 tools/perf/scripts/python/bin/tasks-analyzer-record
> create mode 100755 tools/perf/scripts/python/bin/tasks-analyzer-report
> create mode 100755 tools/perf/scripts/python/tasks-analyzer.py
> --
> 2.30.2
>
Powered by blists - more mailing lists