From: Roberto Spadim <roberto@spadim.com.br>
To: "Keld Jørn Simonsen" <keld@keldix.com>
Cc: David Brown <david@westcontrol.com>, linux-raid@vger.kernel.org
Subject: Re: Mirrored volume peformance questions
Date: Wed, 4 May 2011 12:43:24 -0300 [thread overview]
Message-ID: <BANLkTimten+bOJpsoDERDsE2CH1MT_NQ7g@mail.gmail.com> (raw)
In-Reply-To: <20110504081339.GB414@www2.open-std.org>
i think that a good add to today read balance could be add disk
acess_time (1/rpm, 0 for 'non rotational', 1 for unknow)
head_distance * acess_time, could allow a better select of disks or
mix of 7200/10000/15000 rpm disks
maybe it can be read from disk information at assemble time, i don't
know if disk speed (rpm) can be read from device block (some disks
display information with hdparm and smartctl)
it's not a 1000% improvement, it's 1% at high read/write load
2011/5/4 Keld Jørn Simonsen <keld@keldix.com>:
> On Wed, May 04, 2011 at 09:42:40AM +0200, David Brown wrote:
>> raid10,far is better for sequential reads - it gives better-than-raid0
>> performance on average since it will do striped reads from the faster
>> outer tracks. And for multi-threaded reads, it should also be a little
>> faster than other raid10 layouts (and raid1, which is much the same as
>> raid10,near). Since it prefers to get the data from the outer half, you
>> get the benefits of short-stroking your disks - faster transfer speeds
>> and less head movement.
>>
>> The cost of raid10,far is greater head movement for writes - but that is
>> not the OP's main concern.
>
> yes, in theory this is so. But two reasons almost eliminates this in
> practice. First, the processes do not wait for completion of the IO of
> writes, the processes only deliver the data to the file buffer cache of
> the kernel, which then periodically flushes the data to the disk drives.
> Second, the flushing of the data is ordered so that the collected data
> buffers are written as much sequentially as possible to the drives.
> This goes for all Linux MD RAID1/RAID10 layouts. Given that random
> writes are random over the whole set of drives, for any mirrored
> raid1/raid10 layout, the flushing of the data is about the same.
>
> best regards
> keld
> --
> 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
prev parent reply other threads:[~2011-05-04 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 19:42 Mirrored volume peformance questions Morad, Steve
2011-05-03 19:52 ` Roberto Spadim
2011-05-03 21:34 ` Keld Jørn Simonsen
2011-05-03 21:40 ` Roberto Spadim
2011-05-04 7:42 ` David Brown
2011-05-04 8:13 ` Keld Jørn Simonsen
2011-05-04 15:43 ` Roberto Spadim [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=BANLkTimten+bOJpsoDERDsE2CH1MT_NQ7g@mail.gmail.com \
--to=roberto@spadim.com.br \
--cc=david@westcontrol.com \
--cc=keld@keldix.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).