From: Robert L Mathews <lists@tigertech.com>
To: Mdadm <linux-raid@vger.kernel.org>
Subject: Re: Why are reads not balanced across my RAID-1?
Date: Sat, 25 Jan 2014 09:52:44 -0800	[thread overview]
Message-ID: <52E3F9EC.3000901@tigertech.com> (raw)
In-Reply-To: <CAH3kUhGA8x_5hDbqxcskHQq+5YXFrz4XspmzeTq0O8dQci8zzw@mail.gmail.com>
On 1/24/14, 10:22 AM, Roberto Spadim wrote:
> i don't know there's space to improvement here, i got 1% of speed up
> doing a mix of disk speed (7.2k rpm 5k rpm and 15k rpm and a ssd) and
> changing the read balance algorithm
If your RAID1 array contains both spinning disks and SSDs, you can (and
should) simply set the spinning disks as "write-mostly":
 http://tansi.info/hybrid/
This causes all reads to come from the SSD if possible.
After doing this, all reads should be at the SSD speed, although all
writes will still be at spinning disk speeds. We have been doing this on
all our database servers for years with zero problems (although we
finally now trust SSDs enough to switch all array members to SSDs, so
we're phasing it out).
If your workload consists of lots of scattered reads, you'll get far
more than a 1% read performance increase from this, with no tweaking of
read balancing algorithm necessary.
-- 
Robert L Mathews, Tiger Technologies, http://www.tigertech.net/
     prev parent reply	other threads:[~2014-01-25 17:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 10:47 Why are reads not balanced across my RAID-1? George Spelvin
2014-01-24 12:04 ` keld
2014-01-24 13:33   ` George Spelvin
2014-01-25  1:48     ` keld
2014-01-24 14:56   ` Matt Garman
2014-01-24 16:50     ` Mathias Burén
2014-01-24 17:49     ` keld
2014-01-24 18:22       ` Roberto Spadim
2014-01-25  1:18         ` George Spelvin
2014-01-30 20:05           ` Phillip Susi
2014-01-25 17:52         ` Robert L Mathews [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=52E3F9EC.3000901@tigertech.com \
    --to=lists@tigertech.com \
    --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).