From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
xfs@oss.sgi.com, Alan Piszcz <ap@solarrain.com>
Subject: Re: Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors
Date: Thu, 12 Jun 2008 15:08:48 -0400 [thread overview]
Message-ID: <48517440.6020905@tmr.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0806111652550.18136@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Wed, 11 Jun 2008, Justin Piszcz wrote:
>
>>
>>
>> On Wed, 11 Jun 2008, Bill Davidsen wrote:
>>
>>> Justin Piszcz wrote:
>>>> First, the original benchmarks with 6-SATA drives with fixed
>>>> formatting, using
>>>> right justification and the same decimal point precision throughout:
>>>> http://home.comcast.net/~jpiszcz/20080607/raid-benchmarks-decimal-fix-and-right-justified/disks.html
>>>> Now for for veliciraptors! Ever wonder what kind of speed is
>>>> possible with
>>>> 3 disk, 4,5,6,7,8,9,10-disk RAID5s? I ran a loop to find out, each
>>>> run is
>>>> executed three times and the average is taken of all three runs per
>>>> each RAID5 disk set.
>>>>
>>>> In short? The 965 no longer does justice with faster drives, a new
>>>> chipset
>>>> and motherboard are needed. After reading or writing to 4-5
>>>> veliciraptors
>>>> it saturates the bus/965 chipset.
>>>
>>> This is very interesting, but a 16GB chunk size bears no
>>> relationship to anything I would run in the real world, and I
>>> suspect most people are in the same category.
>>
>> I based my bonnie++ test on:
>> http://everything2.org/?node_id=1479435
>>
>> So I could compare to his results.
>>
>> I use a 1024k (1MiB) with 16384 stripe, this offered the best overall
>> read/write/rewrite performance AFAIK.
>
> 1024k chunk size (raid5 chunk size)
> echo 16384 > stripe_cache_size
Please don't explain any more, I'm confused enough already. I can't make
those numbers match 16G no matter how I add them, either the contents of
the column labeled "size:chunk size" isn't the size of the chunk, or you
have a multiplier floating around that I don't see. And you eliminated
the degraded performance, since your stripe_cache_size is less than
(raid5 chunk size)*(#disks), I would expect the reads in degraded mode
to be dog slow because the don't fit in cache, even if 1024k is what I
call chunk size and certainly not if chunk size is 16G.
--
Bill Davidsen <davidsen@tmr.com>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark
prev parent reply other threads:[~2008-06-12 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-07 14:22 Linux MD RAID 5 Benchmarks Across (3 to 10) 300 Gigabyte Veliciraptors Justin Piszcz
2008-06-07 15:54 ` David Lethe
2008-06-08 1:46 ` Dan Williams
2008-06-09 7:51 ` thomas62186218
2008-06-09 8:43 ` Keld Jørn Simonsen
2008-06-09 13:41 ` David Lethe
2008-06-09 14:27 ` Keld Jørn Simonsen
2008-06-09 14:56 ` David Lethe
2008-06-09 23:15 ` Keld Jørn Simonsen
2008-06-11 17:02 ` Nat Makarevitch
2008-06-11 20:27 ` Bill Davidsen
2008-06-11 20:48 ` Justin Piszcz
2008-06-11 20:53 ` Justin Piszcz
2008-06-12 19:08 ` Bill Davidsen [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=48517440.6020905@tmr.com \
--to=davidsen@tmr.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).