From: David Chinner <dgc@sgi.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: David Chatterton <dchatterton@aconex.com>,
'xfs-dev' <xfs-dev@sgi.com>, 'xfs-oss' <xfs@oss.sgi.com>,
'David Chinner' <dgc@sgi.com>
Subject: Re: Review: Concurrent Multi-File Data Streams
Date: Tue, 15 May 2007 10:05:23 +1000 [thread overview]
Message-ID: <20070515000523.GQ86004887@sgi.com> (raw)
In-Reply-To: <20070514223946.GA19487@one.firstfloor.org>
On Tue, May 15, 2007 at 12:39:46AM +0200, Andi Kleen wrote:
> > So yes this is designed for a workload where the number of AGs is a multiple
> > of the number of streams since mixing streams in the one AG is the problem
> > it tries to avoid.
>
> Sounds like a awful special case. Is that common?
Common enough to be a serious problem when running multiple 2k ingest and
playout streams (320MB/s each).
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-05-15 0:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 0:36 Review: Concurrent Multi-File Data Streams David Chinner
2007-05-12 18:46 ` Andi Kleen
2007-05-13 3:08 ` Eric Sandeen
2007-05-14 5:35 ` Review: Concurrent Multi-File Data Streams - centisecs Timothy Shimmin
[not found] ` <000001c79544$44076ac0$0501010a@DCHATTERTONLAPTOP>
2007-05-14 22:39 ` Review: Concurrent Multi-File Data Streams Andi Kleen
2007-05-15 0:05 ` David Chinner [this message]
2007-05-15 0:15 ` David Chatterton
2007-05-13 20:59 ` Christoph Hellwig
2007-05-15 6:23 ` David Chinner
2007-05-15 9:23 ` Christoph Hellwig
2007-09-20 1:31 ` Hxsrmeng
2007-09-21 9:13 ` Leon Kolchinsky
2007-09-21 12:55 ` David Chinner
[not found] ` <1190399077.3795.86.camel@localhost.localdomain>
2007-09-23 7:45 ` David Chinner
2007-09-23 15:47 ` Ming Zhang
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=20070515000523.GQ86004887@sgi.com \
--to=dgc@sgi.com \
--cc=andi@firstfloor.org \
--cc=dchatterton@aconex.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@oss.sgi.com \
/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.