mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: roy@karlsbakk.net, <linux-kernel@vger.kernel.org>
Subject: Re: Tuning Linux for high-speed disk subsystems
Date: Tue, 13 Nov 2001 09:58:45 -0600 (CST)	[thread overview]
Message-ID: <200111131558.JAA58186@tomcat.admin.navo.hpc.mil> (raw)

Roy Sigurd Karlsbakk <roy@karlsbakk.net>:
> 
> Hi all
> 
> After some testing at Compaq's lab in Oslo, I've come to the conclusion
> that Linux cannot scale higher than about 30-40MB/sec in or out of a
> hardware or software RAID-0 set with several stripe/chunk sizes tried out.
> The set is based on 5 18GB 10k disks running SCSI-3 (160MBps) alone on a
> 32bit/33MHz PCI bus.
> 
> After speking to the storage guys here, I was told the problem generally
> was that the OS should send the data requests at 256kB block sizes, as the
> drives (10k) could handle 100 I/O operations per second, and thereby could
> give a total of (256*100)kB/sec per spindle. When using smaller block
> sizes, the speed would decrease in a linear fasion.
> 
> Does anyone know this stuff good enough to help me how to tune the system?
> PS: The CPUs were almost idle during the test. Tested file system was
> ext2.

I shouldn't be the authoritative answer on this, but to start with:

a. You don't provide enough info on the hardware configuration:

	a. are all of the drives on one SCSI controller?
	b. is there only one PCI?
	c. since you mention "CPUs", how many, and which ones
	d. which chipset?
	e. what was used for the benchmark?
	f. which hardware raids were tested?

b. Your mentioned limit (40MB/sec) sounds like it is really a
   memory<->bridge<->PCI<->controller bandwidth limit - this is about what I
   get from a SCSI-3 alone on 33MHz bus (I use SCSI 3 for system disk, SCSI 2
   for audio/CDRW/tape drive).

c. Based on the statement that the "CPUs were almost idle", it sounds like
   the limit is outside the OS. If you are trying to setup a disk server then
   you should check into multiple PCI busses @ 66MHz, and multiple disk
   controllers.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

             reply	other threads:[~2001-11-13 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 15:58 Jesse Pollard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-22 10:15 Martin Knoblauch
2001-11-22 16:30 ` Andreas Dilger
     [not found] <3B6867E6CB09B24385A73719A50C7C9A79791F@athena.boxxtech.com>
2001-11-16 16:53 ` Marvin Justice
2001-11-16  2:56 Dieter Nützel
2001-11-16 11:51 ` Roy Sigurd Karlsbakk
2001-11-16 15:24   ` Dieter Nützel
2001-11-13 20:38 Torrey Hoffman
2001-11-13 14:29 Roy Sigurd Karlsbakk
2001-11-13 16:43 ` Ragnar Kjørstad
2001-11-13 16:51 ` Alan Cox
2001-11-13 17:59 ` Craig I. Hagan
2001-11-13 16:18   ` Marcelo Tosatti
2001-11-14 10:33   ` Roy Sigurd Karlsbakk
2001-11-14 10:35   ` Roy Sigurd Karlsbakk
2001-11-13 20:00 ` Dan Hollis

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=200111131558.JAA58186@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --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

all inboxes | Powered by JetHome®