From: Valdis.Kletnieks@vt.edu
To: Jonathan Johnson <johnsonn@matc.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How do I self diagnose slow write to HDD performance issue
Date: Tue, 21 Oct 2008 23:07:25 -0400 [thread overview]
Message-ID: <111655.1224644845@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 21 Oct 2008 14:34:01 CDT." <48FDE860.8C56.0056.0@matc.edu>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Tue, 21 Oct 2008 14:34:01 CDT, Jonathan Johnson said:
> Before I setup the array I tested the SATA 2 drives connected to the mobo SATA connect and got approx 60mb/s
> write and even better read speeds per drive.
Remember that streaming read/write speed is usually only a small part of the
total disk performance story. Sure, if you don't have to move the heads much,
you can go 60 megabytes/sec. However, even the *hottest* drives out there
have a hard time sustaining 200 seeks per second.
In other words, every time you have to move the heads, it costs you 300Kbytes/sec
of throughput (1/200th of that 60M).
And bonnie++ probably moves the heads a lot.
To *add* insult to injury, if you're running in RAID6 mode, each time you write
to the RAID set, it has to do *several* I/Os to do all the parity computations.
So you take a 300K hit for each of those I/Os.
There's a *reason* why RAID1 is still used - you can (assuming a smart enough
controller) launch both the write and the mirroring write at the same time in
parallel, taking little or no performance penalty.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2008-10-22 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 19:34 Jonathan Johnson
2008-10-22 3:07 ` Valdis.Kletnieks [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=111655.1224644845@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=johnsonn@matc.edu \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®