From: Roberto Spadim <roberto@spadim.com.br>
To: Andras Korn <korn@raidlist.elan.rulez.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: write-behind has no measurable effect?
Date: Wed, 16 Feb 2011 12:00:41 -0300 [thread overview]
Message-ID: <AANLkTinus5p_A0sADMv7Z=+xnfdfwnRRo8p_-uye3ddD@mail.gmail.com> (raw)
In-Reply-To: <20110216120056.GD13135@hellgate.intra.guy>
a question here...
what happen if all disks are write-mostly and just ssd is write-behind?
why?
write-behind is an async feature (md only return ok to filesystem if
non write-behind disks are sync writen)
write-mostly is a read_balance optimization (ony read from that device
if all non-write-mostly devices fail)
making all disks write-mostly could allow us to use write-behind on
slowest(s) disk(s)
another idea...
could we change raid1 write code? how?
if a total of X write are done, return ok to filesystem, all other
devices are marked as write-behind (automatic write-behind) after sync
writes disks are marked as non-write-behind again
maybe a optimization is: what disk MUST be sync(only non
write-behind), what disk MUST BE async (only write-behind), what disk
can be async/sync (any write-behind type)
another question...
can read balance use write-mostly device in a very busy system without
failed devices (all mirrors are in sync)?
2011/2/16 Andras Korn <korn@raidlist.elan.rulez.org>:
> On Tue, Feb 15, 2011 at 06:10:17AM -0300, Roberto Spadim wrote:
>
>> andras could you make some benchmarks to raid1 with round robin read balance?
>> at this site:
>> www.spadim.com.br/raid1/
>
> For the record: we did some benchmarks and while the patch shows promise and
> seems to cause no problems, it resulted in no measurable performance
> increase for a RAID1 array composed of an SSD and two 7200rpm HDDs.
>
> Andras
>
> --
> Andras Korn <korn at elan.rulez.org>
> If it ain't broken, play with it until it is.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-16 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 21:38 write-behind has no measurable effect? Andras Korn
2011-02-14 22:50 ` NeilBrown
2011-02-14 22:57 ` Andras Korn
2011-02-14 23:41 ` NeilBrown
2011-02-15 1:00 ` Andras Korn
2011-02-15 1:19 ` John Robinson
2011-02-15 2:19 ` Andras Korn
[not found] ` <AANLkTikFSOePZJXknAt=Tx6+FpdJ4tiSNwpuwuPC3RY=@mail.gmail.com>
2011-02-15 9:10 ` Roberto Spadim
2011-02-15 12:40 ` Andras Korn
2011-02-15 13:26 ` Roberto Spadim
2011-02-15 17:46 ` Roberto Spadim
2011-02-16 12:00 ` Andras Korn
2011-02-16 15:00 ` Roberto Spadim [this message]
2011-02-14 22:56 ` Doug Dumitru
2011-02-14 23:03 ` Andras Korn
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='AANLkTinus5p_A0sADMv7Z=+xnfdfwnRRo8p_-uye3ddD@mail.gmail.com' \
--to=roberto@spadim.com.br \
--cc=korn@raidlist.elan.rulez.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 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).