All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Announce] Development release 0.1 of the LatencyTOP tool
Date: Fri, 18 Jan 2008 12:02:11 -0700	[thread overview]
Message-ID: <1200682931.7735.18.camel@localhost> (raw)
In-Reply-To: <4790E3A6.7060807@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]


On Fri, 2008-01-18 at 09:36 -0800, Arjan van de Ven wrote:
> The Intel Open Source Technology Center is pleased to announce the
> release of version 0.1 of LatencyTOP, a tool for developers to visualize
> system latencies.
> 
> http://www.latencytop.org
> 
> Slow servers, Skipping audio, Jerky video --everyone knows the symptoms
> of latency. But to know what's really going on in the system, what's causing
> the latency, and how to fix it... those are difficult questions without
> good answers right now.
[cut]

Just curious...

My biggest latency problems (as observed by me, the user) happen when a
program needs memory, or launching a new program, and the kernel begins
forces dirty memory to disk.  This results in an unholy seek storm of
mixed writes (flushing, maybe a little swap) and reads (new program
loading).  Streaming audio/video almost always starts freezing up during
this as well.

I don't suppose LatencyTop would help track anything down in that case,
would it?
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-01-18 19:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18 17:36 [Announce] Development release 0.1 of the LatencyTOP tool Arjan van de Ven
2008-01-18 17:39 ` [patch 1/3] LatencyTOP infrastructure patch Arjan van de Ven
2008-01-20 11:34   ` Helge Deller
2008-01-20 16:47   ` Dmitry Adamushko
2008-01-20 17:18     ` Dmitry Adamushko
2008-01-21  8:06   ` KOSAKI Motohiro
2008-01-21 16:16     ` Arjan van de Ven
2008-01-18 17:40 ` [patch 2/3] Latencytop instrumentations part 1 Arjan van de Ven
2008-01-18 22:26   ` Frank Ch. Eigler
2008-01-18 22:33     ` Arjan van de Ven
2008-01-18 22:47       ` Arnaldo Carvalho de Melo
2008-01-18 23:11       ` Frank Ch. Eigler
2008-01-18 23:20         ` Arjan van de Ven
2008-01-18 17:42 ` [patch 3/3] LatencyTOP instrumentations part 2 Arjan van de Ven
2008-01-18 18:27 ` [Announce] Development release 0.1 of the LatencyTOP tool Roberto Fichera
2008-01-18 18:35   ` Arjan van de Ven
2008-01-18 18:46     ` Roberto Fichera
2008-01-18 19:02 ` Zan Lynx [this message]
2008-01-19  5:07 ` Andi Kleen
2008-01-19  5:16   ` Arjan van de Ven
2008-01-19  5:27     ` Andi Kleen
2008-01-19  5:25       ` Arjan van de Ven
2008-01-19  5:33         ` Andi Kleen
2008-01-19  5:34           ` Arjan van de Ven
2008-01-19  6:08             ` Andi Kleen
2008-01-19  5:37           ` [Announce] Development release 0.1 of the LatencyTOP tool II Andi Kleen
2008-01-21  0:52 ` Development release 0.1 of the LatencyTOP tool KOSAKI Motohiro

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=1200682931.7735.18.camel@localhost \
    --to=zlynx@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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.