linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Linux Raid Study <linuxraid.study@gmail.com>
Cc: "Majed B." <majedb@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: Raid5 Read Perf drop in 2.6.27
Date: Thu, 10 Sep 2009 19:22:19 +0200	[thread overview]
Message-ID: <20090910172219.GB420@rap.rap.dk> (raw)
In-Reply-To: <f5d1f90a0909091845t744ce5cerdf00fd656ff21c09@mail.gmail.com>

Hi

There is some data on raid5 performance (and other raid types) at our
wiki at: http://linux-raid.osdl.org/index.php/Performance

When you have something you want to share with others, then we can add
your info to the data there, either by a URL or by direct inclusion in
the wiki.

best regards
keld

On Wed, Sep 09, 2009 at 06:45:31PM -0700, Linux Raid Study wrote:
> I build/compile my own kernel..
> 
> Have you done any benchmarks for Read RAID5 perf?
> 
> Thanks!
> 
> On 9/9/09, Majed B. <majedb@gmail.com> wrote:
> > Well, that's my point. To make sure that your kernels are identical in
> >  options, compare the .config files found in /usr/src/linux-<version>
> >
> >  You may find changes and differences in areas like bluetooth,
> >  wireless, ...etc. These don't matter.
> >
> >  Did you compile your own kernel, or are you using one compiled for a
> >  specific distro?
> >
> >  On Thu, Sep 10, 2009 at 4:17 AM, Linux Raid
> >
> > Study<linuxraid.study@gmail.com> wrote:
> >  > Yes - the setup is the same. The only thing that changes is the kernel.
> >  >
> >  > I have 4 HDDs (2 from WD VelociRaptor 150GB/10k RPM and 2 from Seagate
> >  > 320GB/7.2k RPM).  The HDDs are connected using two Silicon Image SATA
> >  > controllers (Sil3132) connected to my host using PCIe.
> >  >
> >  > I use the default kernel scheduling scheme.
> >  >
> >  > Thanks!
> >  >
> >  > On 9/9/09, Majed B. <majedb@gmail.com> wrote:
> >  >> Are you sure you're using the same Kernel Scheduler on both kernels?
> >  >>
> >  >>  Have you checked and verified that the same drivers are being loaded?
> >  >>  (IDE vs. AHCI -- proprietary drivers vs. open source)
> >  >>
> >  >>  This is interesting!
> >  >>
> >  >>
> >  >>  On Thu, Sep 10, 2009 at 1:54 AM, Linux Raid
> >  >>  Study<linuxraid.study@gmail.com> wrote:
> >  >>  > Hello:
> >  >>  >
> >  >>  > I'm benchmarking RAID5 Read performance with 4 disks and notice perf
> >  >>  > drop when using kernel 2.6.27.
> >  >>  > The perf with 2.6.27 is 150MB/s whereas with kernel 2.6.21 (and same
> >  >>  > setup), the perf is 180MB/s/
> >  >>  >
> >  >>  >
> >  >>  >
> >  >>  > Some of the tests I have done:
> >  >>  > 1. I ran  experiments using iozone also but notice that READ perf with
> >  >>  > RAID5 in 2.6.27 is ~30% less as compared to 2.6.21.
> >  >>  > Write perf is similar but Read is an issue.
> >  >>  >
> >  >>  > 2. On 2.6.27, I played around with chunk size and blocksize parameters
> >  >>  > and got ~5% improvement but not much. I used following cmds:
> >  >>  >
> >  >>  > #mdadm --create /dev/md0 --level=5 --assume-clean --raid-devices=4
> >  >>  > /dev/sda /dev/sdb /dev/sdc /dev/sdd --chunk=32
> >  >>  > #mke2fs -b 4096 -E stride=8 /dev/md0
> >  >>  >
> >  >>  > #time dd if=/dev/md0 of=/dev/null bs=94208 count=1024
> >  >>  >
> >  >>  >
> >  >>  > Is this perf drop a known issue? Can someone please recommend some
> >  >>  > performance tuning tips?
> >  >>  >
> >  >>  > Thanks a lot for your time and help!
> >  >>
> >  >> > --
> >  >>  > 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
> >  >>  >
> >  >>
> >  >>
> >  >>
> >  >>  --
> >  >>
> >  >>        Majed B.
> >  >>
> >  >
> >
> >
> >
> >
> > --
> >
> >        Majed B.
> >
> --
> 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

  parent reply	other threads:[~2009-09-10 17:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 22:54 Raid5 Read Perf drop in 2.6.27 Linux Raid Study
2009-09-09 23:52 ` Majed B.
2009-09-10  1:17   ` Linux Raid Study
2009-09-10  1:27     ` Majed B.
2009-09-10  1:45       ` Linux Raid Study
2009-09-10  9:37         ` Majed B.
2009-09-10 17:22         ` Keld Jørn Simonsen [this message]
2009-09-10 21:57           ` Linux Raid Study
2009-09-10 23:55             ` Greg Freemyer
2009-09-16 23:45           ` Linux Raid Study
2009-09-17  4:12             ` Majed B.
2009-09-17  7:50               ` Linux Raid Study
2009-09-16  7:57   ` Linux Raid Study
2009-09-16  8:06     ` Majed B.
2009-09-16  8:10       ` Linux Raid Study
     [not found]         ` <70ed7c3e0909160119m3c26af4fx667cc257c9dc79e6@mail.gmail.com>
2009-09-16  8:21           ` Majed B.
2009-09-16  8:46             ` Linux Raid Study
2009-09-16 17:58               ` Linux Raid Study

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=20090910172219.GB420@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=linux-raid@vger.kernel.org \
    --cc=linuxraid.study@gmail.com \
    --cc=majedb@gmail.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).