All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Alex Turner <armtuk@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>, Arshavir Grigorian <ag@m-cam.com>,
	linux-raid@vger.kernel.org, pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Postgres on RAID5
Date: 14 Mar 2005 15:17:11 -0500	[thread overview]
Message-ID: <87zmx6rni0.fsf@stark.xeocode.com> (raw)
In-Reply-To: <33c6269f050314115339b6861d@mail.gmail.com>


Alex Turner <armtuk@gmail.com> writes:

> a 14 drive stripe will max out the PCI bus long before anything else,

Hopefully anyone with a 14 drive stripe is using some combination of 64 bit
PCI-X cards running at 66Mhz...

> the only reason for a stripe this size is to get a total accessible
> size up.  

Well, many drives also cuts average latency. So even if you have no need for
more bandwidth you still benefit from a lower average response time by adding
more drives.

-- 
greg


  reply	other threads:[~2005-03-14 20:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 19:48 Postgres on RAID5 Arshavir Grigorian
2005-03-14  4:36 ` [PERFORM] " Greg Stark
2005-03-14  7:44   ` [PERFORM] Postgres on RAID5 (possible sync blocking read type issue on 2.6.11) David Greaves
2005-03-14 19:53   ` [PERFORM] Postgres on RAID5 Alex Turner
2005-03-14 20:17     ` Greg Stark [this message]
2005-03-14 20:35       ` Jim Buttafuoco
2005-03-14 21:03     ` Arshavir Grigorian
2005-03-14 22:47       ` Michael Tokarev
2005-03-14 23:49         ` Guy
2005-03-15 16:17           ` Effect of Stripe Size (was Postgres on RAID5) Ruth Ivimey-Cook
2005-03-16 16:47 ` Postgres on RAID5 David Dougall
2005-03-16 16:55   ` Michael Tokarev

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=87zmx6rni0.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=ag@m-cam.com \
    --cc=armtuk@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=pgsql-performance@postgresql.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.