From: Isaac Huang <He.Huang@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] using LST for performance testing
Date: Thu, 08 Oct 2009 15:42:25 -0400 [thread overview]
Message-ID: <20091008194225.GX4767@sun.com> (raw)
In-Reply-To: <4AC23B21.2030207@cray.com>
On Tue, Sep 29, 2009 at 11:51:45AM -0500, Nic Henke wrote:
> ......
> > The test servers concurrently posts one passive buffer for each
> > request, so for each test request there's one LNetMDAttach and one
> > unlink operation and both operations need to grab the one big
> > LNET_LOCK therefore it could be possible that the server CPU becomes a
> > bottleneck before the network could be saturated. The solution is to,
> > instead of one request per buffer, post one big buffer that could
> > accommodate multiple requests to amortize the per buffer processing
> > costs.
> >
> If we added timestamps to the data, the processing time & buffer sizing
> would be less of an issue - it wouldn't factor into the accuracy of the
> numbers are are gathering.
Probably not. The timestamps affect only the stat gathering RPCs which
should be far out numbered by the test RPCs (loop x concurrency x
test_client_count, for each test server).
Isaac
prev parent reply other threads:[~2009-10-08 19:42 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
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 [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=20091008194225.GX4767@sun.com \
--to=he.huang@sun.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.