public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lionel Bouton <Lionel.Bouton@free.fr>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux i/o tweaking
Date: Thu, 15 Nov 2001 23:32:09 +0100	[thread overview]
Message-ID: <3BF44269.3000402@free.fr> (raw)
In-Reply-To: <Pine.LNX.4.30.0111151930360.14530-100000@mustard.heime.net>

Roy Sigurd Karlsbakk wrote:

>>I guess the question I'd ask would be what kinda number do you expect from
>>the raid 5 stripe. 107MB/s sounds like a reasonable number from a two
>>channel u160 controller...
>>
>
>I really don't know. My 'logical' mind told me I could get close-to
>speed-per-disk * number-of-disks, but it might be wrong.
>
>
>>my previous best is around 89MB/s with 4 cheetah 15K 18gb drives raid/0
>>
>
>I had 5 drives per SCSI bus and the controller was sitting alone on a
>66MHz/64bit PCI hose.  I really can't see where the bottleneck is!
>
# Hdparm
Do you use hdparm for your test ?

What gives hdparm -T (timing buffer-cache reading) ?
I believe it's kind of a hard ceiling...

<jealousy>
I use single channel PC66 sdram on a BX chipset here and have only 60 
MB/s from buffer-cache on a SMP 2.4.13-ac2 kernel. Seeing a complain for 
107 MB/s from a disk subsystem makes me feel somehow frustrated :-)
</jealousy>

# Hardware
Are all drives recognised as 160 MB/s capable devices ? SCSI is so 
touchy, you never know...
Look in /var/log/dmesg for the scsi adapter logs.

# Software
What's your kernel version. Any patch applied ?

# Looking for a clue
You may try to profile the kernel on arrays with different numbers of 
disks in raid 0 (to keep cpu out of equation at first).
It could help to find the bandwidth or the number of disks where the 
actual speedup begins to fall behind the theoritical speedup and then 
have the profiles at hand.

-- 
 Lionel Bouton

-
"I wanted to be free, so I opensourced my whole DNA code" Gyver, 1999.




      reply	other threads:[~2001-11-15 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-15 16:13 Linux i/o tweaking Roy Sigurd Karlsbakk
2001-11-15 16:22 ` Jens Axboe
2001-11-15 16:32   ` Roy Sigurd Karlsbakk
2001-11-15 16:41     ` Jakob Østergaard
2001-11-15 16:50       ` Roy Sigurd Karlsbakk
2001-11-15 18:17 ` Joel Jaeggli
2001-11-15 18:33   ` Roy Sigurd Karlsbakk
2001-11-15 22:32     ` Lionel Bouton [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=3BF44269.3000402@free.fr \
    --to=lionel.bouton@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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