linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ming Zhang <mingz@ele.uri.edu>
To: Guy <bugzilla@watkins-home.com>
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: RE: raid0 low performance
Date: Fri, 01 Jul 2005 10:42:51 -0400	[thread overview]
Message-ID: <1120228971.5501.19.camel@localhost.localdomain> (raw)
In-Reply-To: <1120223833.5507.40.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

i wrote another program to read from device and then discard.

./synctest /dev/md1
Personalities : [linear] [raid0] [raid1] [raid5] [multipath]
read_ahead 1024 sectors
md1 : active raid0 sdl[3] sdk[2] sdb[1] sda[0]
      1562845184 blocks 64k chunks

unused devices: <none>
 1048576Bytes *     1024 :   158.459MB/s
  524288Bytes *     2048 :   164.935MB/s
  262144Bytes *     4096 :   173.649MB/s
  131072Bytes *     8192 :   174.228MB/s
   65536Bytes *    16384 :   178.462MB/s
   32768Bytes *    32768 :   177.569MB/s
   16384Bytes *    65536 :   177.888MB/s
    8192Bytes *    65536 :   173.809MB/s
    4096Bytes *   131072 :   172.732MB/s
    2048Bytes *   131072 :   165.512MB/s
    1024Bytes *   131072 :   150.354MB/s


so looks like the bus is not a bottleneck here. and read ahead really
works here.

i guess the problem is r/w disparity in controller or driver.

thanks guys

ming



On Fri, 2005-07-01 at 09:17 -0400, Ming Zhang wrote:
> On Fri, 2005-07-01 at 08:55 -0400, Guy wrote:
> > I think you should test 2 or more disks at the same time.  This
> would prove
> > that your system can or can't move more than about 60MB/s.
> 
> 
> i tested and seems that 90MB/s is the max here.
> 
> 
> if i run 2 program copy on 2 disks independently on same card, both of
> them bound at 45MB/s
> if i run 3 program copy on 3 disks independently on same card, both of
> them bound at 27 or 28MB/s so total is still 90MB/s
> if i run 2 program copy on 2 disks but one is on 4 port marvel and
> another is 8 port marvel, then both of the bound at 55MB/s which is
> disk
> limitation.
> 
> so i guess the card or bus has problem. i will check bus speed soon.
> 
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-07-01 14:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  2:15 raid0 low performance Ming Zhang
2005-07-01  2:28 ` Tyler
2005-07-01  2:57   ` John Madden
2005-07-01 12:41     ` Ming Zhang
2005-07-01 12:54       ` John Madden
2005-07-01 13:10         ` Ming Zhang
2005-07-01 12:32   ` Ming Zhang
2005-07-01 12:55 ` Guy
2005-07-01 13:17   ` Ming Zhang
2005-07-01 13:54     ` Ming Zhang
2005-07-05  0:13       ` Mark Hahn
2005-07-05  0:26         ` Ming Zhang
2005-07-05 13:19           ` Ming Zhang
2005-07-01 14:42     ` Ming Zhang [this message]

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=1120228971.5501.19.camel@localhost.localdomain \
    --to=mingz@ele.uri.edu \
    --cc=bugzilla@watkins-home.com \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).