From: Frederic Weisbecker <fweisbec@gmail.com>
To: Pierre Tardy <tardyp@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Tom Zanussi <tzanussi@gmail.com>,
Paul Mackerras <paulus@samba.org>
Cc: linux-kernel@vger.kernel.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, arjan@infradead.org,
ziga.mahkovec@gmail.com
Subject: Re: [RFC] PyTimechart
Date: Tue, 11 May 2010 23:36:27 +0200 [thread overview]
Message-ID: <20100511213625.GD5422@nowhere> (raw)
In-Reply-To: <AANLkTilJLcdfK-vgqGdXyaZ_bQ1BDFmQl619egtGAA4i@mail.gmail.com>
On Tue, May 11, 2010 at 11:10:36PM +0200, Pierre Tardy wrote:
> Hello,
>
> PyTimechart is another implementation of two very useful tools
> available for the linux community:
> perf-timechart ( http://blog.fenrus.org/?p=5 ) and bootchart (
> http://www.bootchart.org/ )
>
> The two tools share a common idea of making their output to SVG files.
> While it is a very good idea for small traces, the generated SVG can
> be very heavy, and turns out to be good stress tests for inkscape
> developers...
>
> PyTimechart is a tool that parses ftrace text traces, and display them
> with the help of a very powerful dynamic plot framework, Chaco (
> http://code.enthought.com/chaco/ )
> The GUI makes the best it can to ease the browsing of huge traces.
>
> The best is to look at those two 30s screencasts, to figure out how that work.
>
> a look at mplayer startup:
> http://tardyp.free.fr/pytimechart/mplayer_start.mp4
> a look at ubuntu boot:
> http://tardyp.free.fr/pytimechart/boot.mp4
>
> This tool still is in the state of a prototype, I dont know if it
> worth to continue to improve it or to implement it ideas in LTTV or
> Kernel Shark.
> It is actually very useful in its current form (
> http://elinux.org/images/0/07/Effect_of_wakeups_on_Moorestown_power.pdf
> ), and will work without recompiling the kernel of recent distros.
>
> the source code with build instruction is located here
> http://gitorious.org/pytimechart
>
> What do you think?
I think I've been dreaming about this several times.
I've often used perf timechart lately and I'm really frustrated by
its inherent slowness due to its huge svg files. It's barely usable
with a small trace on two cpus, and it's impossible to go further,
which is really a pity for such a powerful tool.
IMO, this GUI is exactly what we want.
If you could plug it to the perf scripting facilities, I would
be very happy to see it merged in perf tools.
Plugging to the scripting API is really easy, run:
$ perf timechart record
$ sudo ./perf trace -g python
generated Python script: perf-trace.py
Now look at ./perf-trace.py, you'll find all the necessary hooks
generated with a default behaviour (displaying traces), which
you can observe by launching:
$ perf trace -s perf-trace.py
You just need to change it to plug your app on it.
(Adding more Cc).
next prev parent reply other threads:[~2010-05-11 21:36 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 21:10 [RFC] PyTimechart Pierre Tardy
2010-05-11 21:36 ` Frederic Weisbecker [this message]
2010-05-12 13:37 ` Pierre Tardy
2010-05-12 14:48 ` Frederic Weisbecker
2010-05-12 15:36 ` Steven Rostedt
2010-05-12 16:46 ` Perf and ftrace [was Re: PyTimechart] Frederic Weisbecker
2010-05-12 17:00 ` Peter Zijlstra
2010-05-12 17:07 ` Mathieu Desnoyers
2010-05-12 17:47 ` Peter Zijlstra
2010-05-12 17:53 ` Mathieu Desnoyers
2010-05-12 18:00 ` Peter Zijlstra
2010-05-12 18:04 ` Mathieu Desnoyers
2010-05-12 18:08 ` Peter Zijlstra
2010-05-12 18:37 ` Mathieu Desnoyers
2010-05-12 18:46 ` Steven Rostedt
2010-05-12 20:27 ` Mathieu Desnoyers
2010-05-12 22:21 ` Steven Rostedt
2010-05-13 13:20 ` Mathieu Desnoyers
2010-05-13 15:42 ` Steven Rostedt
2010-05-13 16:31 ` Mathieu Desnoyers
2010-05-13 16:46 ` Steven Rostedt
2010-05-13 17:10 ` Mathieu Desnoyers
2010-05-13 18:33 ` Steven Rostedt
2010-05-14 7:53 ` Peter Zijlstra
2010-05-12 18:49 ` Peter Zijlstra
2010-05-12 18:51 ` Mathieu Desnoyers
2010-05-12 19:01 ` Peter Zijlstra
2010-05-12 20:52 ` Mathieu Desnoyers
2010-05-12 17:11 ` Ingo Molnar
2010-05-12 16:59 ` [RFC] PyTimechart Ingo Molnar
2010-05-12 17:15 ` Steven Rostedt
2010-05-12 18:23 ` Ingo Molnar
2010-05-12 17:13 ` Pierre Tardy
2010-05-13 15:02 ` Arnaldo Carvalho de Melo
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=20100511213625.GD5422@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.org \
--cc=tardyp@gmail.com \
--cc=tzanussi@gmail.com \
--cc=ziga.mahkovec@gmail.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;
as well as URLs for NNTP newsgroup(s).