From: David Thorburn-Gundlach <davidtg-robot@justpickone.org>
To: Linux RAID list <linux-raid@vger.kernel.org>
Subject: Re: how to know a hard drive will mix well
Date: Sat, 4 Feb 2023 02:20:19 +0000 [thread overview]
Message-ID: <20230204022019.GI25616@jpo> (raw)
In-Reply-To: <CAAMCDedK==A1q-S97=MZGL2Wv_COC4DCGqh__2atSOHk2YBWAg@mail.gmail.com>
Roger, et al --
...and then Roger Heflin said...
% I have mixed many drives, I have never really had a major slowness. At
Good to know.
% worst you will be limited by the drive with the slowest seeks/transfer
% rate. So long as one disk's RPM is not significantly different you should
That's pretty much what I was wondering, but I imagine if it's the same
RPM and the same cache and the same SATA rate it should be ... about the
same.
% not notice it, unless you are running your array right at the limit.
Hmmph. I'm not entirely sure I'm not anyway, but it is just a little PC
mobo running primary and daughtercard SATA ports. A Real Server (tm) is
far, far beyond the current horizon :-)
%
% Technically you may want to also look at another parm that is the sustained
% transfer rate range coming off the platter. This will be a range that is
[snip]
Oh, thanks! Sounds good.
HAND
:-D
--
David T-G
See http://justpickone.org/davidtg/email/
See http://justpickone.org/davidtg/tofu.txt
next prev parent reply other threads:[~2023-02-04 2:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 12:43 how to know a hard drive will mix well David T-G
2023-02-02 18:52 ` Wols Lists
2023-02-02 22:47 ` Pascal Hambourg
2023-02-02 23:27 ` Wol
2023-02-02 23:36 ` Wol
2023-02-04 2:24 ` David Thorburn-Gundlach
[not found] ` <CAAMCDedK==A1q-S97=MZGL2Wv_COC4DCGqh__2atSOHk2YBWAg@mail.gmail.com>
2023-02-04 2:20 ` David Thorburn-Gundlach [this message]
[not found] ` <CAAMCDeerQZyrUG2FAn-y1MA-grb+zDotAYrJvBykqDBhFmAfeQ@mail.gmail.com>
2023-02-05 4:04 ` throughput testing (was "Re: how to know a hard drive will mix well") David Thorburn-Gundlach
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=20230204022019.GI25616@jpo \
--to=davidtg-robot@justpickone.org \
--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 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.