public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Walt H <waltabbyh@mindspring.com>
To: linux-kernel@vger.kernel.org
Subject: Raid0 slowdown from 2.4.19-rc1
Date: Sun, 04 Aug 2002 18:39:50 -0700	[thread overview]
Message-ID: <3D4DD766.1090807@mindspring.com> (raw)


Hello,

I've recently upgraded kernels from 2.4.19-rc1 to rc2 and on to final 
and have experienced a dramatic slowdown in raid0 performance since. 
Final 2.4.19 was patched with XFS and preempt and compiled using 
gcc-3.1.1 - I've tried switching compilers to 2.96 (mandrake 8.2), and 
cutting out preempt patches. First md1 array consists of two partitions 
from hda & hdc. hdparm for both drives looks fine by themselves:

[root@waltsathlon walt]# hdparm -t /dev/hda

/dev/hda:
  Timing buffered disk reads:  64 MB in  1.66 seconds = 38.55 MB/sec
/dev/hdc:
  Timing buffered disk reads:  64 MB in  1.65 seconds = 38.79 MB/sec

However, using them combined as raid0, md1:

/dev/md1:
  Timing buffered disk reads:  64 MB in  1.44 seconds = 44.44 MB/sec

In 2.4.18 and up through 2.4.19-rc1 I saw 66-70MB/sec from this array. 
Starting in rc2 it dropped to the mid 40's. I've also ran bonnie++ and 
confirmed several significant drops, however, not as bad as you would 
think considering the results of hdparm.

Hardware:
Soyo Dragon+ MB w/ Athlon 1800+, 512MB Ram
Drives connected via onboard Promise PDC20265 in ultra mode
2x40GB IBM Deskstar 60GXP (I know....)


Anything else you need, just ask. Please CC me in replies as I'm not a 
member of the list. Thanks,

-Walt


             reply	other threads:[~2002-08-05  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  1:39 Walt H [this message]
     [not found] <Pine.LNX.4.33.0208050040120.15213-100000@coffee.psychology.mcmaster.ca>
2002-08-05 13:54 ` Raid0 slowdown from 2.4.19-rc1 Walt H

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=3D4DD766.1090807@mindspring.com \
    --to=waltabbyh@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    /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