linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ole Olsen <gnu@gmx.net>
To: linux-raid@vger.kernel.org
Subject: Re: slow mdadm reshape, normal?
Date: Thu, 11 Jun 2009 18:07:41 +0200	[thread overview]
Message-ID: <20090611160741.GG30825@rlogin.dk> (raw)
In-Reply-To: <20090611081909.GA16250@cthulhu.home.robinhill.me.uk>

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

Thanks

I was just hoping for something like 127MB/s divided by 3 = 42MB/s which 
is the practical limit of the pci bus assuming each disk gets its equal
share.

6MB/s is only 14% of that, so I wonder where the lost bandwidth goes :)

The reshape takes only 10-15% cpu or so on my 3ghz cpu so dont think that is
the bottleneck.

Might be interesting to test a pci network controller at the same time had I
installed one before the build, that way i could see if the pci bus really got
congested.


On Thu, 11 Jun 2009, Robin Hill wrote:

> On Thu Jun 11, 2009 at 01:36:59AM +0200, Michael Ole Olsen wrote:
> 
> > the slow disks (them with 85MB/s) in the posting are the one on the pci 4x sata controller
> > 
> > the 32bit pci sata (sata_sil) controller has 3 disks connected
> > 
> > the onboard sata2 6x sata connectors have 6 disks connected 
> > (p5n32-e sli motherboard), i believe all these are sata2 and not shared with
> > an ide controller.
> > 
> > so only the pci controller should have bus limitations, but i wonder why it is
> > that slow on reshape compared to build.
> > 
> The build was reading (sequentially) from all drives and writing
> (sequentially) only to one, whereas a reshape is reading from and
> writing to all the drives (including seeking between reads & writes).
> This means it is inevitably a lot slower.  In addition, you're now using
> 3 rather than 2 drives on the PCI bus, which will increase the
> congestion.
> 
> Cheers,
>     Robin
> -- 
>      ___        
>     ( ' }     |       Robin Hill        <robin@robinhill.me.uk> |
>    / / )      | Little Jim says ....                            |
>   // !!       |      "He fallen in de water !!"                 |



[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2009-06-11 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 15:28 FW: Detecting errors on the RAID disks Simon Jackson
2009-05-27 19:35 ` Richard Scobie
2009-05-28  8:19   ` Simon Jackson
     [not found] ` <20090610224055.GW30825@xxxxxxxxx>
2009-06-10 23:36   ` Re: slow mdadm reshape, normal? Michael Ole Olsen
2009-06-11  8:19     ` Robin Hill
2009-06-11 16:07       ` Michael Ole Olsen [this message]
2009-06-11 19:45         ` Michael Ole Olsen
2009-06-11 20:50           ` John Robinson
2009-06-11 21:11             ` slow mdadm reshape, normal? lspci/iostat info Michael Ole Olsen
2009-06-12  0:53           ` slow mdadm reshape, normal? Roger Heflin
  -- strict thread matches above, loose matches on Subject: below --
2009-06-10 22:40 Michael Ole Olsen
2009-06-10 23:04 ` John Robinson

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=20090611160741.GG30825@rlogin.dk \
    --to=gnu@gmx.net \
    --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).