linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: linux-raid@vger.kernel.org
Subject: new bottleneck section in wiki
Date: Wed, 2 Jul 2008 17:56:03 +0200	[thread overview]
Message-ID: <20080702155603.GA11156@rap.rap.dk> (raw)

I should have done something else this afternoon, but anyway, I was
inspired to write up this text for the wiki. Comments welcome.

Keld

Bottlenecks

There can be a number of bottlenecks other than the disk subsystem that
hinders you in getting full performance out of your disks.

One is the PCI bus. Older PCI bus has a 33 MHz cycle and a 32 bit width,
giving a maximum bandwidth of about 1 Gbit/s, or 133 MB/s. This will
easily cause trouble with newer SATA disks which easily gives 70-90 MB/s
each. So do not put your SATA controllers on a 33 MHz PCI bus.

The 66 MHz 64-bit PCI bus is capable of handling about 4 Gbit/s, or
about 500 MB/s. This can also be a bottleneck with bigger arrays, eg a 6
drive array will be able to deliver about 500 MB/s, and maybe you want
also to feed a gigabyte ethernet card - 125 MB/s, totalling potentially
625 MB/s on the PCI bus.

The PCI-Express bus v1.1 has a limit of 250 MB/s per lane per dirction,
and that limit can easily be hit eg by a 4-drive array.

Many SATA controllers are on-board and do not use the PCI bus. Anyway
bandwidth is limited, but it is probably different from motherboard to
motherboard. On board disk controllers most likely have a bigger
bandwidth than IO controllers on a 32-bit PCI 33 MHz, 64-bit PCI 66 MHz,
or PCI-E x1 bus.

Having a RAID connected over the LAN can be a bottleneck, if the LAN
speed is only 1 Gbit/s - this limits the speed of the IO system to 125
MB/s by itself.

Classical bottlenecks are PATA drives placed on the same DMA channel, or
the same PATA cable. This will of cause limit performance, but it should
work, given you have no other means of connecting your disks by. Also
placing more than one element of an array on the same disk hurts
performace seriously, and also gives redundancy problems.

A classical problem is also not to have enabled DMA transfer, or having
lost this setting due to some problem, including not well connected
cables, or setting the transfer speed to less than optimal.

RAM sppec may be a bottleneck. Using 32 bit RAM - or using a 32 bit
operating system may double time spent reading and writing RAM.

CPU usage may be a bottleneck, also combined with slow RAM or only using
RAM in 32-bit mode.

BIOS settings may also impede your performance. 

             reply	other threads:[~2008-07-02 15:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02 15:56 Keld Jørn Simonsen [this message]
2008-07-02 16:43 ` new bottleneck section in wiki Justin Piszcz
2008-07-02 17:21   ` Keld Jørn Simonsen
2008-07-02 17:04 ` David Lethe
2008-07-02 17:51   ` Keld Jørn Simonsen
2008-07-02 18:08     ` David Lethe
2008-07-02 18:26       ` Keld Jørn Simonsen
2008-07-02 21:55         ` Roger Heflin
2008-07-02 19:45       ` Matt Garman
2008-07-02 20:05         ` Keld J?rn Simonsen
2008-07-02 20:24         ` Richard Scobie
2008-07-02 19:03   ` Matt Garman
2008-07-02 19:10     ` Jon Nelson
2008-07-02 19:35       ` Keld J?rn Simonsen
2008-07-02 19:38         ` Jon Nelson
2008-07-02 22:07           ` David Lethe
2008-07-03 12:28             ` Jon Nelson
2008-07-03 14:00               ` Justin Piszcz
2008-07-02 19:17     ` Robin Hill
2008-07-02 19:39     ` Keld J?rn Simonsen
2008-07-03  5:10     ` Doug Ledford
2008-07-02 21:45   ` Roger Heflin
2008-07-02 17:33 ` Iustin Pop
2008-07-02 18:14   ` Keld Jørn Simonsen

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=20080702155603.GA11156@rap.rap.dk \
    --to=keld@dkuug.dk \
    --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).