public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Josef Bacik <jbacik@fb.com>
Cc: a.p.zijlstra@chello.nl, mingo@redhat.com, acme@kernel.org,
	linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH V2] perf-sched: add option to merge like comms to lat output
Date: Sat, 23 May 2015 10:22:21 +0200	[thread overview]
Message-ID: <20150523082221.GA7025@gmail.com> (raw)
In-Reply-To: <1432300720-30478-1-git-send-email-jbacik@fb.com>


* Josef Bacik <jbacik@fb.com> wrote:

> Sometimes when debugging large multi-threaded applications it is helpful to
> collate all of the latency numbers into one bulk record to get an idea of what
> is going on.  This patch does this by merging any entries that belong to the
> same comm into one entry and then spits out those totals.  I've also slightly
> changed the output so you can see how many threads were merged in the
> processing.  Here is the new default output format
> 
>  -----------------------------------------------------------------------------------------------------------------
>   Task                  |   Runtime ms  | Switches | Average delay ms | Maximum delay ms | Maximum delay at       |
>  -----------------------------------------------------------------------------------------------------------------
>   chrome:(23)           |    740.878 ms |     2612 | avg:    0.022 ms | max:    0.845 ms | max at:   7935.254223 s
>   pulseaudio:1523       |     94.440 ms |      597 | avg:    0.027 ms | max:    0.110 ms | max at:   7934.668372 s
>   threaded-ml:6042      |     72.554 ms |      386 | avg:    0.035 ms | max:    1.186 ms | max at:   7935.330911 s
>   Chrome_IOThread:3832  |     52.388 ms |      456 | avg:    0.021 ms | max:    1.365 ms | max at:   7935.330602 s
>   Chrome_ChildIOT:(7)   |     50.694 ms |      743 | avg:    0.021 ms | max:    1.448 ms | max at:   7935.256659 s
>   Compositor:5510       |     30.012 ms |      192 | avg:    0.019 ms | max:    0.131 ms | max at:   7936.636815 s
>   plugin_audio_th:6043  |     24.828 ms |      314 | avg:    0.018 ms | max:    0.143 ms | max at:   7936.205994 s
>   CompositorTileW:(2)   |     14.099 ms |       45 | avg:    0.022 ms | max:    0.153 ms | max at:   7937.521800 s
> 
> the (#) after the task is the number of tasks merged, and then if 
> there were no tasks merged it just shows the pid.  Here is the same 
> trace file with the -p option to print the per-pid latency numbers

Nice!

Acked-by: Ingo Molnar <mingo@kernel.org>

Thanks,

	Ingo

  reply	other threads:[~2015-05-23  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22 13:18 [PATCH V2] perf-sched: add option to merge like comms to lat output Josef Bacik
2015-05-23  8:22 ` Ingo Molnar [this message]
2015-05-27 16:52 ` [tip:perf/core] perf sched: Add " tip-bot for Josef Bacik

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=20150523082221.GA7025@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=jbacik@fb.com \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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