From: "Du, Changbin" <changbin.du@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: changbin.du@intel.com, peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf report: show sort_order in title
Date: Tue, 14 Mar 2017 10:16:44 +0800 [thread overview]
Message-ID: <20170314021644.GA4265@intel.com> (raw)
In-Reply-To: <20170313145718.GP2750@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2938 bytes --]
On Mon, Mar 13, 2017 at 11:57:18AM -0300, Arnaldo Carvalho de Melo wrote:
> > I'll just rename this to use the tools/perf/ style for such functions,
> > making it:
> >
> > static int hists__scnprintf_sort_fields(hists, buf, size)
>
> But then, while testing,
>
> Before:
>
> $ perf report
> Samples: 405 of event 'cycles', Event count (approx.): 101733003
> Overhead Command Shared Object Symbol
> 11.15% swapper [kernel.vmlinux] [k] intel_idle
> 3.00% firefox libxul.so [.] 0x0000000001298b8d
> 1.74% swapper [kernel.vmlinux] [k] update_blocked_averages
> 1.69% qemu-system-x86 [kernel.vmlinux] [k] __fget
> 1.18% swapper [kernel.vmlinux] [k] update_wall_time
>
> Tip: Save output of perf stat using: perf stat record <target workload>
>
> After:
>
> $ perf report
> Samples: 405 of event 'cycles', Event count (approx.): 101733003, Sort by: Children,Overhead,Command,Shared Object,Symbol
> Overhead Command Shared Object Symbol
> 11.15% swapper [kernel.vmlinux] [k] intel_idle
> 3.00% firefox libxul.so [.] 0x0000000001298b8d
> 1.74% swapper [kernel.vmlinux] [k] update_blocked_averages
> 1.69% qemu-system-x86 [kernel.vmlinux] [k] __fget
> 1.18% swapper [kernel.vmlinux] [k] update_wall_time
>
>
> I see now duplication of info, where is the value? Can you show the usecase in
> a compelling way?
>
> - Arnaldo
Thanks for trying. The key idea is to show how does the data sort, especially
the first sort key. When I use some GUI based perf tool, I can see how
my data is sorted by checking the report header status. I think this is
a good for browser.
You are right, the info is duplicated. I got another idea that we show a '↓' at
the header string and only for the first sort key. What do you think?
$ perf report
Samples: 405 of event 'cycles', Event count (approx.): 101733003
↓Overhead Command Shared Object Symbol
11.15% swapper [kernel.vmlinux] [k] intel_idle
3.00% firefox libxul.so [.] 0x0000000001298b8d
1.74% swapper [kernel.vmlinux] [k] update_blocked_averages
Another idea I want to add is to support dynamic sorting. For me, I use perf to
analysing entire system performance, and the data is very large. Then sometimes
it take as long as ~10 minitues to read perf data. So I think if we can change
sort w/o reload data will be good.
--
Thanks,
Changbin Du
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-03-14 2:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 8:36 [PATCH] perf report: show sort_order in title changbin.du
2017-03-13 14:47 ` Arnaldo Carvalho de Melo
2017-03-13 14:57 ` Arnaldo Carvalho de Melo
2017-03-14 2:16 ` Du, Changbin [this message]
2017-03-14 13:04 ` Arnaldo Carvalho de Melo
2017-03-15 2:11 ` Du, Changbin
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=20170314021644.GA4265@intel.com \
--to=changbin.du@intel.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.