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: Tue, 29 Sep 2009 13:02:25 -0500	[thread overview]
Message-ID: <4AC24BB1.8040502@cray.com> (raw)
In-Reply-To: <1254245568.5827.5.camel@lap75545.ornl.gov>

David Dillow wrote:
> On Tue, 2009-09-29 at 11:51 -0500, Nic Henke wrote:
>   
>> I'm wondering if we couldn't add a new 'batch_stat' command. The idea is 
>> that the client code will fill in the start/stop times for each test and 
>> then after the test is done, 'batch_stat' would collect this data. The 
>> collection would still be passive and a new command should minimize the 
>> protocol changes. The per-test data would allow us to get accurate perf 
>> numbers and also provide some data into how parallel the tests were, if 
>> there are any unfairness issues, etc.
>>     
>
> Along these lines, it would be nice if we could specify a run time for
> each test rather than an amount of data to be transferred -- it makes it
> easier to get aggregate bandwidth numbers, and often shows imbalances
> nicely -- the node getting starved is the one that transfers less data.
>   
> It may also make sense to add a 'delay' parameter that causes each test
> to wait a specified amount of time from the 'go' signal. This allows the
> signal to propagate without running into congestion from the test,
> helping to cause all of the clients to start the test closer to
> simultaneously.
>   

Interesting - can you elaborate, perhaps in the form of a patch  ? :-) I 
like both ideas, but not signing up to code them just yet.

Nic

  reply	other threads:[~2009-09-29 18:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 20:33 [Lustre-devel] using LST for performance testing Nic Henke
2009-09-28 17:35 ` Isaac Huang
2009-09-29 16:51   ` Nic Henke
2009-09-29 17:32     ` David Dillow
2009-09-29 18:02       ` Nic Henke [this message]
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=4AC24BB1.8040502@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.