mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com,
	peterz@infradead.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [patch 0/8] Introducing the "timechart" tool
Date: Sat, 12 Sep 2009 16:03:20 +0200	[thread overview]
Message-ID: <20090912140320.GA9292@elte.hu> (raw)
In-Reply-To: <20090912130737.2d55adc0@infradead.org>


* Arjan van de Ven <arjan@infradead.org> wrote:

> [note: since this is a visualization tool, and lkml doesn't like 
> html email, it's probably better to read the online version at
> 
> http://blog.fenrus.org/?p=5
> 
> in which I also show screenshots of the tool. The following text 
> is the first part of the online introduction]
> 
> Finding out why your Linux computer performs the way it does has 
> been a hard task. Sure, there is Oprofile, and even ???perf??? in 
> recent kernels. There is LatencyTOP to find out where latencies 
> happen.
> 
> But all of these tools are rather limited when the software stack 
> that has the performance issue is more complex than a single 
> program. The tool that comes closest to being useful is 
> `bootchart???, but that has a rather limited resolution.
> 
> To solve this, I have been working on a new tool, called 
> Timechart, that has the objective to show on a system level what 
> is going on, at various levels of detail. In fact. one of the 
> design ideas behind timechart is that the output should be 
> ???infinitely zoomable???; that is, if you want to know more 
> details about something, you should be able to zoom in to get 
> these details. The rest of this blog post describes some aspects 
> of timechart, using real life examples and screenshots. However, 
> it is really hard to show the power of timechart on such a static 
> page, to get a real feeling of what timechart can show you really 
> ought to try it out yourself.....

Nice! 'perf timechart' is IMO a really intuitive way to visualize 
perf record output.

Text output goes only so far - patterns of scheduling (and patterns 
of bad behavior) are a lot easier to notice in SVGs.

	Ingo

      reply	other threads:[~2009-09-12 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-12 11:07 Arjan van de Ven
2009-09-12 14:03 ` Ingo Molnar [this message]

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=20090912140320.GA9292@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®