From: Vladimir Milovanovic <vlad@webmail.co.za>
To: Illtud Daniel <illtud.daniel@llgc.org.uk>
Cc: raid-list <linux-raid@vger.kernel.org>
Subject: Re: XP RAID vs md
Date: Fri, 04 Apr 2003 11:21:16 +0200 [thread overview]
Message-ID: <3E8D4E8C.7080503@webmail.co.za> (raw)
In-Reply-To: 3E8D463F.98EFBF1F@llgc.org.uk
Well Daniel what is your take on this? I am very interested in this
since I am working on a project which has to use RAID, and performance
is paramount (after reliability of course). I need to make a decision,
and I would like very much to stick with md, since it is what I know and
am used to. But if one can get huge performance margins using XP, then I
am going to have to consider that.
Cheers,
Vlad.
Illtud Daniel wrote:
>[posted & mailed]
>
>Lars Marowsky-Bree wrote:
>
>
>
>>>Wow... I hope that one of the maintainers will comment on this, I didn't
>>>even know that XP had a sw RAID implementation. Up to 100% more on read
>>>and 60% more on write is quite a significant margin. Is there anything
>>>in favour of the md driver if this is true?
>>>
>>>
>>I've not really checked these numbers yet, so take the following with a grain
>>of salt.
>>
>>
>
>Have a look at http://www.hpl.hp.com/techreports/2002/HPL-2002-352.pdf
>- that'll tell you were the figures are from - the 100% is worst-case.
>
>
>
>>However, with RAID1 for example, I got approximately twice the read speed and
>>95% of the write speed (compared to just using a single disk).
>>
>>
>
>One thing I forgot to mention in my post is that this is all (AFAICS)
>RAID0.
>
>
>
>>I have a really hard time imagining a 100% read boost; that would simply
>>exceed disk bandwidth, and 60% writes - how should that work?
>>
>>
>
>The md driver seriously underperforms at certain request sizes, and
>is generally underperforming. The average boost is less, but still about
>40-60% read and 30-40% write. XP's RAID0 is better than JBOD above a
>certain request size, which is pretty good.
>
>
>
>>I'm not claiming md is perfect or the fastest imaginable solution, but it is
>>rather close to theoretical disk bandwidth. A two digit percentage performance
>>improvement just can't be done.
>>
>>
>
>Well, that's why I asked in my original post for people to look at
>the report. Is isn't that long and it's pretty clear (although short
>on config details).
>
>--
>Illtud Daniel illtud.daniel@llgc.org.uk
>Uwch Ddadansoddwr Systemau Senior Systems Analyst
>Llyfrgell Genedlaethol Cymru National Library of Wales
>Yn siarad drosof fy hun, nid LlGC - Speaking personally, not for NLW
>-
>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:[~2003-04-04 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 12:19 XP RAID vs md Vladimir Milovanovic
2003-04-02 15:27 ` Lars Marowsky-Bree
2003-04-02 20:35 ` Scott McDermott
2003-04-04 8:45 ` Illtud Daniel
2003-04-04 9:21 ` Vladimir Milovanovic [this message]
2003-04-04 9:46 ` Illtud Daniel
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 15:17 Rechenberg, Andrew
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=3E8D4E8C.7080503@webmail.co.za \
--to=vlad@webmail.co.za \
--cc=illtud.daniel@llgc.org.uk \
--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).