pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alex Turner <armtuk@gmail.com>
To: Greg Stark <gsstark@mit.edu>
Cc: Jim C. Nasby <decibel@decibel.org>
Cc: William Yu <wyu@talisys.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: How to improve db performance with $7K?
Date: Wed, 6 Apr 2005 22:06:47 -0500
Message-ID: <33c6269f050406200623d43daf@mail.gmail.com> (raw)
In-Reply-To: <87wtrfmgt5.fsf@stark.xeocode.com>
References: <424840AE.3050200@sfnet.cc>
	<42515198.9090903@sfnet.cc>
	<33c6269f05040412126b5bc719@mail.gmail.com>
	<d30377$1jn8$1@news.hub.org>
	<33c6269f050406083533d2045d@mail.gmail.com>
	<d31f71$2epm$1@news.hub.org>
	<33c6269f050406151241b01148@mail.gmail.com>
	<20050406224102.GM93835@decibel.org>
	<33c6269f0504061732195f6ae4@mail.gmail.com>
	<87wtrfmgt5.fsf@stark.xeocode.com>

Yeah - the more reading I'm doing - the more I'm finding out.

Alledgelly the Western Digial Raptor drives implement a version of
ATA-4 Tagged Queing which allows reordering of commands.  Some
controllers support this.  The 3ware docs say that the controller
support both reordering on the controller and to the drive. *shrug*

This of course is all supposed to go away with SATA II which as NCQ,
Native Command Queueing.  Of course the 3ware controllers don't
support SATA II, but a few other do, and I'm sure 3ware will come out
with a controller that does.

Alex Turner
netEconomist

On 06 Apr 2005 23:00:54 -0400, Greg Stark <gsstark@mit.edu> wrote:
> 
> Alex Turner <armtuk@gmail.com> writes:
> 
> > SATA gives each drive it's own channel, but you have to share in SCSI.
> >  A SATA controller typicaly can do 3Gb/sec (384MB/sec) per drive, but
> > SCSI can only do 320MB/sec across the entire array.
> 
> SCSI controllers often have separate channels for each device too.
> 
> In any case the issue with the IDE protocol is that fundamentally you can only
> have a single command pending. SCSI can have many commands pending. This is
> especially important for a database like postgres that may be busy committing
> one transaction while another is trying to read. Having several commands
> queued on the drive gives it a chance to execute any that are "on the way" to
> the committing transaction.
> 
> However I'm under the impression that 3ware has largely solved this problem.
> Also, if you save a few dollars and can afford one additional drive that
> additional drive may improve your array speed enough to overcome that
> inefficiency.
> 
> --
> greg
> 
>



view thread (119+ messages)  latest in thread

Message-ID: <33c6269f050406200623d43daf@mail.gmail.com>
Permalink:  ../33c6269f050406200623d43daf@mail.gmail.com/
Also on:    postgresql.org/message-id/33c6269f050406200623d43daf@mail.gmail.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: armtuk@gmail.com, gsstark@mit.edu, decibel@decibel.org, wyu@talisys.com
  Subject: Re: How to improve db performance with $7K?
  In-Reply-To: <33c6269f050406200623d43daf@mail.gmail.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