From: Bill Davidsen <davidsen@tmr.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Mattias Wadenstein <maswan@acc.umu.se>,
linux-raid@vger.kernel.org, apiszcz@solarrain.com
Subject: Re: Linux RAID Partition Offset 63 cylinders / 30% performance hit?
Date: Thu, 20 Dec 2007 10:18:09 -0500 [thread overview]
Message-ID: <476A87B1.10403@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712191629190.21347@p34.internal.lan>
Justin Piszcz wrote:
>
>
> On Wed, 19 Dec 2007, Bill Davidsen wrote:
>
>> I'm going to try another approach, I'll describe it when I get
>> results (or not).
>
> http://home.comcast.net/~jpiszcz/align_vs_noalign/
>
> Hardly any difference at whatsoever, only on the per char for
> read/write is it any faster..?
Am I misreading what you are doing here... you have the underlying data
on the actual hardware devices 64k aligned by using either the whole
device or starting a partition on a 64k boundary? I'm dubious that you
will see a difference any other way, after all the translations take place.
I'm trying creating a raid array using loop devices created with the
"offset" parameter, but I suspect that I will wind up doing a test after
just repartitioning the drives, painful as that will be.
>
> Average of 3 runs taken:
>
> $ cat align/*log|grep ,
> p63,8G,57683,94,86479,13,55242,8,63495,98,147647,11,434.8,0,16:100000:16/64,1334210,10,330,2,120,1,3978,10,312,2
>
> p63,8G,57973,95,76702,11,50830,7,62291,99,136477,10,388.3,0,16:100000:16/64,1252548,6,296,1,115,1,7927,20,373,2
>
> p63,8G,57758,95,80847,12,52144,8,63874,98,144747,11,443.4,0,16:100000:16/64,1242445,6,303,1,117,1,6767,17,359,2
>
>
> $ cat noalign/*log|grep ,
> p63,8G,57641,94,85494,12,55669,8,63802,98,146925,11,434.8,0,16:100000:16/64,1353180,8,314,1,117,1,8684,22,283,2
>
> p63,8G,57705,94,85929,12,56708,8,63855,99,143437,11,436.2,0,16:100000:16/64,12211519,29,297,1,113,1,3218,8,325,2
>
> p63,8G,57783,94,78226,11,48580,7,63487,98,137721,10,438.7,0,16:100000:16/64,1243229,8,307,1,120,1,4247,11,313,2
>
>
--
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
next prev parent reply other threads:[~2007-12-20 15:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 14:50 Linux RAID Partition Offset 63 cylinders / 30% performance hit? Justin Piszcz
2007-12-19 15:01 ` Mattias Wadenstein
2007-12-19 15:04 ` Justin Piszcz
2007-12-19 15:06 ` Jon Nelson
2007-12-19 15:31 ` Justin Piszcz
2007-12-20 10:37 ` Gabor Gombas
2007-12-19 17:40 ` Bill Davidsen
2007-12-19 17:37 ` Jon Nelson
2007-12-19 17:37 ` Jon Nelson
2007-12-19 17:55 ` Justin Piszcz
2007-12-19 19:18 ` Bill Davidsen
2007-12-19 19:44 ` Justin Piszcz
2007-12-19 21:31 ` Justin Piszcz
2007-12-20 15:18 ` Bill Davidsen [this message]
2007-12-20 15:00 ` Justin Piszcz
2007-12-20 10:24 ` Gabor Gombas
2007-12-20 10:33 ` Gabor Gombas
2007-12-19 21:44 ` Michal Soltys
2007-12-19 22:12 ` Jon Nelson
2007-12-20 13:01 ` Michal Soltys
2007-12-19 21:59 ` Robin Hill
2007-12-19 22:03 ` Justin Piszcz
2007-12-25 19:06 ` Bill Davidsen
2007-12-29 17:22 ` dean gaudet
2007-12-29 17:34 ` Justin Piszcz
2007-12-30 1:33 ` Michael Tokarev
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=476A87B1.10403@tmr.com \
--to=davidsen@tmr.com \
--cc=apiszcz@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@vger.kernel.org \
--cc=maswan@acc.umu.se \
/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).