All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nic Henke <nic@cray.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] using LST for performance testing
Date: Thu, 24 Sep 2009 15:33:18 -0500	[thread overview]
Message-ID: <4ABBD78E.50506@cray.com> (raw)

Hello,

	I'm hoping to get a few ideas on how we could modify LST to make doing 
performance testing easier. Right now we can use "lst stat" to get a 
rough idea of performance, but the timers are pretty rough and the data 
is a snapshot.

	Any ideas ? I've got cycles to do the coding, but not sure what would 
be the best way to fit this into the existing LST framework.


BTW - the ability to dump CSV or some other text file with per-node and 
per-group data would also be nice.

Nic

             reply	other threads:[~2009-09-24 20:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 20:33 Nic Henke [this message]
2009-09-28 17:35 ` [Lustre-devel] using LST for performance testing Isaac Huang
2009-09-29 16:51   ` Nic Henke
2009-09-29 17:32     ` David Dillow
2009-09-29 18:02       ` Nic Henke
2009-09-30 13:53         ` David Dillow
2009-10-08 19:36       ` Isaac Huang
2009-09-29 18:03     ` Nic Henke
2009-10-05 11:09     ` Eric Barton
2009-10-05 14:02       ` Nic Henke
2009-10-08 19:42     ` Isaac Huang

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=4ABBD78E.50506@cray.com \
    --to=nic@cray.com \
    --cc=lustre-devel@lists.lustre.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.