From: Max Waterman <davidmaxwaterman+gmane@fastmail.co.uk>
To: linux-raid@vger.kernel.org
Subject: Re: Poor RAID6 performance on frankenstein server
Date: Sun, 25 Dec 2005 18:07:06 +0800 [thread overview]
Message-ID: <dolr6m$5hv$1@sea.gmane.org> (raw)
In-Reply-To: <20051225023230.GA5047@pog.tecnopolis.ca>
Trevor Cordes wrote:
> ...However, the way the Plextor works is the audio is
> software-encoded into MP3 on the fly (ie: not in the Plextor like the
> video).
I would be tempted to look at the path the audio takes from the plextor
to the disk. Clearly it goes via the CPU. Seems like there's a
bottleneck there somewhere - some bus bandwidth issues (does USB share
the same bus as the disk [ie PCI] at any point?) - I don't know that
chipset (Intel 845D). Does it depend on which disk array you copy to/from?
...but, no, I don't really know what I'm talking about...so take it for
what it's worth.
Max.
next prev parent reply other threads:[~2005-12-25 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 2:32 Poor RAID6 performance on frankenstein server Trevor Cordes
2005-12-25 10:07 ` Max Waterman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-25 17:23 Andrew Burgess
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='dolr6m$5hv$1@sea.gmane.org' \
--to=davidmaxwaterman+gmane@fastmail.co.uk \
--cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).