pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Alex Turner <armtuk@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>
Cc: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: 18 Apr 2005 11:43:54 -0400
Message-ID: <878y3gks3p.fsf@stark.xeocode.com> (raw)
In-Reply-To: <33c6269f0504180817511b27a3@mail.gmail.com>
References: <CC74E7E10A8A054798B6611BD1FEF4D30625DA5B@vamail01.thexchange.com>
	<425EBA0C.6030804@sfnet.cc>
	<d3vpnn$2iu$1@news.hub.org>
	<87pswsku6e.fsf@stark.xeocode.com>
	<33c6269f0504180817511b27a3@mail.gmail.com>


Alex Turner <armtuk@gmail.com> writes:

> This is fundamentaly untrue.
> 
> A mirror is still a mirror.  At most in a RAID 10 you can have two
> simultaneous seeks.  You are always going to be limited by the seek
> time of your drives.  It's a stripe, so you have to read from all
> members of the stripe to get data, requiring all drives to seek. 
> There is no advantage to seek time in adding more drives.  

Adding drives will not let you get lower response times than the average seek
time on your drives*. But it will let you reach that response time more often. 

The actual response time for a random access to a drive is the seek time plus
the time waiting for your request to actually be handled. Under heavy load
that could be many milliseconds. The more drives you have the fewer requests
each drive has to handle.

Look at the await and svctime columns of iostat -x.

Under heavy random access load those columns can show up performance problems
more accurately than the bandwidth columns. You could be doing less bandwidth
but be having latency issues. While reorganizing data to allow for more
sequential reads is the normal way to address that, simply adding more
spindles can be surprisingly effective.

> By adding more drives you can increase throughput, but the max throughput of
> the PCI-X bus isn't that high (I think around 400MB/sec) You can easily get
> this with a six or seven drive RAID 5, or a ten drive RAID 10. At that point
> you start having to factor in the cost of a bigger chassis to hold more
> drives, which can be big bucks.

You could use software raid to spread the drives over multiple PCI-X cards.
But if 400MB/s isn't enough bandwidth then you're probably in the realm of
"enterprise-class" hardware anyways.

* (Actually even that's possible: you could limit yourself to a portion of the
  drive surface to reduce seek time)

-- 
greg




view thread (119+ messages)  latest in thread

Message-ID: <878y3gks3p.fsf@stark.xeocode.com>
Permalink:  ../878y3gks3p.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/878y3gks3p.fsf@stark.xeocode.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: gsstark@mit.edu, armtuk@gmail.com, wyu@talisys.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <878y3gks3p.fsf@stark.xeocode.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox