All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Pekka Enberg <penberg@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] perf report: Add a simple GTK2-based 'perf report' browser
Date: Thu, 23 Feb 2012 14:53:02 -0200	[thread overview]
Message-ID: <20120223165302.GG25177@infradead.org> (raw)
In-Reply-To: <20120223164739.GF25177@infradead.org>

Em Thu, Feb 23, 2012 at 02:47:39PM -0200, Arnaldo Carvalho de Melo escreveu:
> Em Thu, Feb 23, 2012 at 06:45:04PM +0200, Pekka Enberg escreveu:
> > On Thu, 2012-02-23 at 14:39 -0200, Arnaldo Carvalho de Melo wrote:
> > > > Dunno, probably. Does that matter, though? It's pretty damn fast as-is.
> > > 
> > > Well, what kinds of perf.data file are you feeding it?
> > 
> > It's a real-world case where I'm profiling JRuby startup under Jato with
> > perf:
> > 
> > penberg@jaguar:~/src/jato$ ls -lh perf.data 
> > -rw------- 1 penberg penberg 453K 2012-02-23 18:06 perf.data
> > 
> > On Thu, 2012-02-23 at 14:39 -0200, Arnaldo Carvalho de Melo wrote:
> > > I'm testing it now with large ones, lets see.
> > 
> > How big files are we talking about here?
> 
> 5 MB ones, say.

Nah:

[root@felicio linux]# perf record -a -F 10000 sleep 5m
[ perf record: Woken up 166 times to write data ]
[ perf record: Captured and wrote 42.104 MB perf.data (~1839573 samples)
]
[root@felicio linux]# 
[root@felicio linux]# 
[root@felicio linux]# perf report --gtk

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                                                                                                                           
10618 root      20   0  408m 170m  49m S  0.0  2.2   0:04.71 perf

[root@felicio linux]# perf report --tui

10633 root      20   0  379m 165m  45m S  0.0  2.1   0:01.15 perf
 
> But the way you did it is pretty minimalistic, which is good, its just
> that I don't really like the idea of having two mirror data structures
> representing the report lines.

- Arnaldo

  reply	other threads:[~2012-02-23 16:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 16:18 [PATCH] perf report: Add a simple GTK2-based 'perf report' browser Pekka Enberg
2012-02-23 16:28 ` Arnaldo Carvalho de Melo
2012-02-23 16:32   ` Pekka Enberg
2012-02-23 16:39     ` Arnaldo Carvalho de Melo
2012-02-23 16:45       ` Pekka Enberg
2012-02-23 16:47         ` Arnaldo Carvalho de Melo
2012-02-23 16:53           ` Arnaldo Carvalho de Melo [this message]
2012-02-23 17:10             ` Pekka Enberg
2012-02-23 17:37               ` Arnaldo Carvalho de Melo
2012-02-23 17:52                 ` Pekka Enberg
2012-02-24  0:58                   ` Namhyung Kim
2012-02-24  6:36                     ` Pekka Enberg
2012-03-19 20:08                   ` [tip:perf/core] " tip-bot for Pekka Enberg
2012-02-23 19:36 ` [PATCH] " Colin Walters
2012-02-23 20:18   ` Pekka Enberg
2012-02-23 20:33     ` Colin Walters
2012-02-23 21:27       ` Pekka Enberg
2012-02-24  9:48         ` Ingo Molnar
2012-02-24 10:05           ` Pekka Enberg
2012-03-16 19:48             ` Arnaldo Carvalho de Melo
2012-03-19 18:12             ` Arnaldo Carvalho de Melo
2012-03-27 10:26               ` 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=20120223165302.GG25177@infradead.org \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --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 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.