From: koan <koan00@gmail.com>
To: "Rui Santos" <rsantos@grupopie.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Slow Soft-RAID 5 performance
Date: Wed, 18 Jul 2007 14:07:36 -0400 [thread overview]
Message-ID: <64d833020707181107o705ff16ava129e91fcf68a8ef@mail.gmail.com> (raw)
In-Reply-To: <469E4A70.1000306@grupopie.com>
Are you sure about that chunk size? In you initial posting you show
/proc/mdstat reporting:
"md2 : active raid5 sdc3[2] sda3[0] sdb3[1]
780083968 blocks level 5, 128k chunk, algorithm 2 [3/3] [UUU]"
Which would seem to state a 128K chunk, and thus with a 4k block size
you would need a stride of 32.
On 7/18/07, Rui Santos <rsantos@grupopie.com> wrote:
> koan wrote:
> > How did you create the ext3 filesystem?
>
> The chunk_size is at 256KB, ext3 block size is 4k. I believe the correct
> option that should be passed trough to --stride is 64.
> Am I correct ?
>
> I've also tested ( after sending my first report ) with xfs.
> I've also increases readahead to 65535 on all HD's
> I've also increases the stripe_cache_size to 16384.
>
> I can now get ~100MB/sec...
>
> >
> > Did you use the appropriate --stride option as noted here:
> > http://tldp.org/HOWTO/Software-RAID-HOWTO-5.html (#5.11)
> > -
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
> >
> >
>
>
next prev parent reply other threads:[~2007-07-18 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 14:07 koan
2007-07-18 17:14 ` Rui Santos
2007-07-18 18:07 ` koan [this message]
2007-07-19 11:43 ` Rui Santos
-- strict thread matches above, loose matches on Subject: below --
2007-07-18 9:56 Rui Santos
2007-07-18 10:28 ` Justin Piszcz
2007-07-18 14:49 ` J.A. Magallón
2007-07-18 17:17 ` Rui Santos
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=64d833020707181107o705ff16ava129e91fcf68a8ef@mail.gmail.com \
--to=koan00@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rsantos@grupopie.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
all inboxes | Powered by JetHome®