All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Where is the performance bottleneck?
Date: Wed, 31 Aug 2005 09:11:26 +0200	[thread overview]
Message-ID: <20050831071126.GA7502@midnight.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0508301919250.25574@diagnostix.dwd.de>

On Tue, Aug 30, 2005 at 08:06:21PM +0000, Holger Kiehl wrote:
> >>How does one determine the PCI-X bus speed?
> >
> >Usually only the card (in your case the Symbios SCSI controller) can
> >tell. If it does, it'll be most likely in 'dmesg'.
> >
> There is nothing in dmesg:
> 
>    Fusion MPT base driver 3.01.20
>    Copyright (c) 1999-2004 LSI Logic Corporation
>    ACPI: PCI Interrupt 0000:02:04.0[A] -> GSI 24 (level, low) -> IRQ 217
>    mptbase: Initiating ioc0 bringup
>    ioc0: 53C1030: Capabilities={Initiator,Target}
>    ACPI: PCI Interrupt 0000:02:04.1[B] -> GSI 25 (level, low) -> IRQ 225
>    mptbase: Initiating ioc1 bringup
>    ioc1: 53C1030: Capabilities={Initiator,Target}
>    Fusion MPT SCSI Host driver 3.01.20
> 
> >To find where the bottleneck is, I'd suggest trying without the
> >filesystem at all, and just filling a large part of the block device
> >using the 'dd' command.
> >
> >Also, trying without the RAID, and just running 4 (and 8) concurrent
> >dd's to the separate drives could show whether it's the RAID that's
> >slowing things down.
> >
> Ok, I did run the following dd command in different combinations:
> 
>    dd if=/dev/zero of=/dev/sd?1 bs=4k count=5000000

I think a bs of 4k is way too small and will cause huge CPU overhead.
Can you try with something like 4M? Also, you can use /dev/full to avoid
the pre-zeroing.

> Here the results:
> 
>    Each disk alone
>    /dev/sdc1 59.094636 MB/s
>    /dev/sdd1 58.686592 MB/s
>    /dev/sde1 55.282807 MB/s
>    /dev/sdf1 62.271240 MB/s
>    /dev/sdg1 60.872891 MB/s
>    /dev/sdh1 62.252781 MB/s
>    /dev/sdi1 59.145637 MB/s
>    /dev/sdj1 60.921119 MB/s

>    All 8 disks in parallel
>    /dev/sdc1 24.120545 MB/s
>    /dev/sdd1 24.419801 MB/s
>    /dev/sde1 24.296588 MB/s
>    /dev/sdf1 25.609548 MB/s
>    /dev/sdg1 24.572617 MB/s
>    /dev/sdh1 25.552590 MB/s
>    /dev/sdi1 24.575616 MB/s
>    /dev/sdj1 25.124165 MB/s

You're saturating some bus. It almost looks like it's the PCI-X,
although that should be able to deliver up (if running at the full speed
of AMD8132) up to 1GB/sec, so it SHOULD not be an issue.

> So from these results, I may assume that md is not the cause of the problem.
> 
> What comes as a big surprise is that I loose 25% performance with only
> two disks and each hanging on its own channel!
> 
> Is this normal? I wonder if other people have the same problem with
> other controllers or the same.

No, I don't think this is OK.

> What can I do next to find out if this is a kernel, driver or hardware
> problem?
 
You need to find where the bottleneck is, by removing one possible
bottleneck at a time in your test.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

  reply	other threads:[~2005-08-31  7:11 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-29 18:20 Where is the performance bottleneck? Holger Kiehl
2005-08-29 19:54 ` Mark Hahn
2005-08-30 19:08   ` Holger Kiehl
2005-08-30 23:05     ` Guy
2005-09-28 20:04       ` Bill Davidsen
2005-09-30  4:52         ` Guy
2005-09-30  5:19           ` dean gaudet
2005-10-06 21:15           ` Bill Davidsen
2005-08-29 20:10 ` Al Boldi
2005-08-30 19:18   ` Holger Kiehl
2005-08-31 10:30     ` Al Boldi
2005-08-29 20:25 ` Vojtech Pavlik
2005-08-30 20:06   ` Holger Kiehl
2005-08-31  7:11     ` Vojtech Pavlik [this message]
2005-08-31  7:26       ` Jens Axboe
2005-08-31 11:54         ` Holger Kiehl
2005-08-31 12:07           ` Jens Axboe
2005-08-31 13:55             ` Holger Kiehl
2005-08-31 14:24               ` Dr. David Alan Gilbert
2005-08-31 20:56                 ` Holger Kiehl
2005-08-31 21:16                   ` Dr. David Alan Gilbert
2005-08-31 16:20               ` Jens Axboe
2005-08-31 15:16                 ` jmerkey
2005-08-31 16:58                   ` Tom Callahan
2005-08-31 16:58                     ` Tom Callahan
2005-08-31 15:47                     ` jmerkey
2005-08-31 17:11                   ` Jens Axboe
2005-08-31 15:59                     ` jmerkey
2005-08-31 17:32                       ` Jens Axboe
2005-08-31 16:51                 ` Holger Kiehl
2005-08-31 17:35                   ` Jens Axboe
2005-08-31 19:00                     ` Holger Kiehl
2005-08-31 18:06                   ` Michael Tokarev
2005-08-31 18:52                     ` Ming Zhang
2005-08-31 18:57                       ` Ming Zhang
2005-08-31 12:24           ` Nick Piggin
2005-08-31 16:25             ` Holger Kiehl
2005-08-31 17:25               ` Nick Piggin
2005-08-31 21:57                 ` Holger Kiehl
2005-09-01  9:12                   ` Holger Kiehl
2005-09-02 14:28                     ` Al Boldi
2005-08-31 13:38       ` Holger Kiehl
2005-08-29 23:09 ` Peter Chubb

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=20050831071126.GA7502@midnight.ucw.cz \
    --to=vojtech@suse.cz \
    --cc=Holger.Kiehl@dwd.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.