From: Ingo Molnar <mingo@kernel.org>
To: Pekka Enberg <penberg@iki.fi>
Cc: David Ahern <dsahern@gmail.com>,
Pekka Enberg <penberg@kernel.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf trace: Simplify '--summary' output
Date: Wed, 13 Nov 2013 12:14:30 +0100 [thread overview]
Message-ID: <20131113111430.GA9654@gmail.com> (raw)
In-Reply-To: <528322F3.5050008@iki.fi>
* Pekka Enberg <penberg@iki.fi> wrote:
> On 11/12/13 11:40 PM, Ingo Molnar wrote:
> >So if you prefer unit-less lines that's defensible, perhaps output the
> >unit somewhere else:
> >
> > syscall calls min avg max stddev
> > (msec) (msec) (msec) (%)
> > --------------- -------- -------- -------- -------- ------
> > sendmsg 2 0.002 0.005 0.008 55.00
> > recvmsg 2 0.002 0.003 0.005 44.00
> > epoll_wait 1 0.000 0.000 0.000 0.00
> >
> >or so?
>
> Looks good. I'll make a patch later today unless someone else beats
> me to it.
Maybe this variant is even better:
syscall calls min avg max stddev
(msec) (msec) (msec) (%)
--------------- -------- -------- -------- -------- ------
sendmsg 2 0.002 0.005 0.008 55.0%
recvmsg 2 0.002 0.003 0.005 44.0%
epoll_wait 1 0.000 0.000 0.000 0.0%
Note how we can squeeze the % into that column by using only single digit
precision percentage - double digit is pretty pointless IMO.
Also note that the different nature of the stddev column stands out better
if there's four more horizontal spaces separating it from the other
colums.
But maybe it's just me.
Btw., the msec colums seem a bit narrow, they allow up to 9999.999msec
values which is 10 seconds. If any delay is larger than that then what
happens, do the values get unaligned in an ugly fashion like they so often
do in 'vmstat'? Maybe space for one or two digits more would give it more
breathing space:
syscall calls min avg max stddev
(msec) (msec) (msec) (%)
--------------- -------- --------- --------- --------- ------
sendmsg 2 0.002 0.005 0.008 55.0%
recvmsg 2 0.002 0.003 0.005 44.0%
epoll_wait 1 0.000 0.000 0.000 0.0%
This still looks directly pasteable into email and commit logs and looks
nicely compact on my terminals as well.
Thanks,
Ingo
next prev parent reply other threads:[~2013-11-13 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-12 14:42 [PATCH] perf trace: Simplify '--summary' output Pekka Enberg
2013-11-12 21:33 ` Ingo Molnar
2013-11-12 21:36 ` David Ahern
2013-11-12 21:38 ` Pekka Enberg
2013-11-12 21:42 ` David Ahern
2013-11-12 21:50 ` Ingo Molnar
2013-11-12 21:40 ` Ingo Molnar
2013-11-13 6:57 ` Pekka Enberg
2013-11-13 11:14 ` Ingo Molnar [this message]
2013-11-12 21:56 ` [tip:perf/urgent] " tip-bot for Pekka Enberg
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=20131113111430.GA9654@gmail.com \
--to=mingo@kernel.org \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=penberg@iki.fi \
--cc=penberg@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).