From: Brian J. Murrell <Brian.Murrell@Sun.COM>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] parallelism across oss or ost?
Date: Mon, 26 Nov 2007 12:55:48 -0500 [thread overview]
Message-ID: <1196099748.31044.4.camel@pc.ilinx> (raw)
In-Reply-To: <200711261703.lAQH369U028247@cmf.nrl.navy.mil>
On Mon, 2007-11-26 at 12:03 -0500, chas williams - CONTRACTOR wrote:
> if i have a single oss with multiple ost's do i get any parallelism
> when striping across the ost's?
If the hardware can handle it. i.e. as long as the bandwidth between
the clients and the OSS is capable and as long as the bandwidth and/or
connect paths to the disk can handle it.
We have many installations with >1 OST/OSS simply because usually, the
bandwidth of a single disk is much less than the next slowest component
in and out of a single OSS.
> i.e. would a client form multiple
> connections on whatever transport between the itself the oss?
If you are asking what I think you are, yes. Maybe not as literally as
you are asking, but logically, yes. A client will utilize multiple OSTs
in an OSS, in parallel if the file access patterns dictate such.
b.
prev parent reply other threads:[~2007-11-26 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 17:03 [Lustre-devel] parallelism across oss or ost? chas williams - CONTRACTOR
2007-11-26 17:55 ` Brian J. Murrell [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=1196099748.31044.4.camel@pc.ilinx \
--to=brian.murrell@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.