public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Seger <Mark.Seger@hp.com>
To: linux-kernel@vger.kernel.org, util-linux-ng@vger.kernel.org
Cc: Karel Zak <kzak@redhat.com>, Andrea Righi <a.righi@cineca.it>,
	Balbir Singh <balbir@in.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Latest release of collectl can now show top processes sorted by I/O
Date: Thu, 12 Jun 2008 07:14:50 -0400	[thread overview]
Message-ID: <4851052A.80008@hp.com> (raw)

This felt significant enough to announce to a wider audience.  If you 
haven't heard of collectl before, see: 
http://collectl.sourceforge.net/index.html, as monitoring processes is 
just a small component of what it can do and besides the 'usual set of 
suspects' such as cpu, network, disk and memory it can also monitor less 
common types of data such as nfs, slabs, lustre, quadrics, infiniband 
and even interrupts by cpu!  To read more about its capabilities see 
http://collectl.sourceforge.net/Features.html

The short story on I/O is you can now say "collectl --top io" and see a 
dynamically sorted list of top I/O users, displayed once a second, 
assuming of course that you're using a kernel that supports this.  If 
you include --procopts t, you can also see the top threads as well.  
Unfortunately there's a bug in the way I/O stats are currently reported 
in that if you just look at a process and not its threads, the aggregate 
is not included and so you can see I/O rates of 0 while the threads are 
working their little hearts out.  Andrea Righi has published a patch 
that corrects this and both his patch and my original bugzilla can be 
found at the bottom of the page that describes process monitoring in 
more detail at http://collectl.sourceforge.net/Process.html.  Just one 
comment, and I tried to be more descriptive in the webpage, looking for 
new processes/threads can be pretty labor intensive and by applying 
appropriate filters or taking less frequent samples you can 
significantly reduce the system load.

-mark



                 reply	other threads:[~2008-06-12 11:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4851052A.80008@hp.com \
    --to=mark.seger@hp.com \
    --cc=a.righi@cineca.it \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=kzak@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=util-linux-ng@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox