From: Nick Piggin <piggin@cyberone.com.au>
To: Mattias Wadenstein <maswan@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Performance issue with 2.6 md raid0
Date: Fri, 06 Feb 2004 02:40:23 +1100 [thread overview]
Message-ID: <402263E7.6010903@cyberone.com.au> (raw)
In-Reply-To: <Pine.A41.4.58.0402051304410.28218@lenin.acc.umu.se>
Mattias Wadenstein wrote:
>Greetings.
>
>While testing a file server to store a couple of TB in resonably large
>files (>1G), I noticed an odd performance behaviour with the md raid0 in a
>pristine 2.6.2 kernel as compared to a 2.4.24 kernel.
>
>When striping two md raid5:s, instead of going from about 160-200MB/s for
>a single raid5 to 300M/s for the raid0 in 2.4.24, the 2.6.2 kernel gave
>135M/s in single stream read performance.
>
>
Can you try booting with elevator=deadline please?
next prev parent reply other threads:[~2004-02-05 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 15:23 Performance issue with 2.6 md raid0 Mattias Wadenstein
2004-02-05 15:40 ` Nick Piggin [this message]
2004-02-05 16:03 ` Timothy Miller
2004-02-05 16:04 ` Mattias Wadenstein
2004-02-06 2:17 ` Nick Piggin
2004-02-06 2:34 ` Neil Brown
2004-02-06 14:54 ` Mattias Wadenstein
2004-02-06 19:33 ` Bill Davidsen
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=402263E7.6010903@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@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