From: Stan Hoeppner <stan@hardwarefreak.com>
To: Adam Goryachev <mailinglists@websitemanagers.com.au>
Cc: linux-raid <linux-raid@vger.kernel.org>
Subject: Re: RAID10 Performance
Date: Fri, 27 Jul 2012 02:07:24 -0500 [thread overview]
Message-ID: <50123E2C.8090108@hardwarefreak.com> (raw)
In-Reply-To: <50115123.1020900@websitemanagers.com.au>
On 7/26/2012 9:16 AM, Adam Goryachev wrote:
> I've got a system with the following config that I am trying to improve
> performance on. Hopefully you can help guide me in the best direction
> please.
> 3 x 2TB WDC WD2003FYYS-02W0B1
...
> The three HDD's are configured in a single RAID10
...
> Which is then shared with DRBD to another identical system.
> Then LVM is used to carve the redundant storage into virtual disks
> Finally, iSCSI is used to export the virtual disks to the various
> virtual machines running on other physical boxes.
>
> When a single VM is accessing data, performance is more than acceptable
> (max around 110M/s as reported by dd)
>
> The two SAN machines have 1 Gb ethernet crossover between them, and 4 x
> Gb bonded to the switch which connects to the physical machines running
> the VM's (which have only a single Gb connection).
>
> The issue is poor performance when more than one machine attempts to do
> disk intensive activity at the same time (ie, when the anti virus scan
> starts on all VM's at the same time, or during the backup window, etc).
...
I'm really surprised you don't already know the answer, and that you
gave such a lengthy detailed description.
Your problem is very simple. It is suffered by many people, who lack
basic understanding of rotating drive performance in relation to their
workloads.
You don't have enough seek bandwidth. The drive heads simply can't move
fast enough to service all sector requests in a timely manner. There is
no way to fix this by tweaking the operating system. You need to
increase your seek rate.
1. Recreate the arrays with 6 or 8 drives each, use a 64KB chunk
2. Replace the 7.2k WD drives with 10k SATA, or 15k SAS drives
3. Replace the drives with SSDs
Any of these 3 things will decrease latency per request.
--
Stan
next prev parent reply other threads:[~2012-07-27 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 14:16 RAID10 Performance Adam Goryachev
2012-07-27 7:07 ` Stan Hoeppner [this message]
2012-07-27 13:02 ` Adam Goryachev
2012-07-27 18:29 ` Stan Hoeppner
2012-07-28 6:36 ` Adam Goryachev
2012-07-28 15:33 ` Stan Hoeppner
2012-08-08 3:49 ` Adam Goryachev
2012-08-08 16:59 ` Stan Hoeppner
2012-08-08 17:14 ` Roberto Spadim
2012-08-09 1:00 ` Adam Goryachev
2012-08-09 22:37 ` Stan Hoeppner
2012-07-27 12:05 ` Phil Turmel
-- strict thread matches above, loose matches on Subject: below --
2011-03-02 9:04 Aaron Sowry
2011-03-02 9:24 ` Robin Hill
2011-03-02 10:14 ` Keld Jørn Simonsen
2011-03-02 14:42 ` Mark Knecht
2011-03-02 14:47 ` Mathias Burén
2011-03-02 15:02 ` Mario 'BitKoenig' Holbe
2011-03-02 8:50 Aaron Sowry
2011-03-02 11:16 ` NeilBrown
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=50123E2C.8090108@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
/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.