pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-performance@postgresql.org, "Merlin Moncure" <merlin.moncure@rcsonline.com>
Cc: alex@neteconomist.com
Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
Date: 14 Jan 2005 13:47:34 -0500
Message-ID: <874qhjvoe1.fsf@stark.xeocode.com> (raw)
In-Reply-To: <200501140936.08654.josh@agliodbs.com>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A75B4@Herge.rcsinc.local>
	<200501140936.08654.josh@agliodbs.com>

Josh Berkus <josh@agliodbs.com> writes:

> Merlin,
> 
> > I think the danger about SATA is that many SATA components are not
> > server quality, so you have to be more careful about what you buy.  For
> > example, you can't just assume your SATA backplane has hot swap lights
> > (got bit by this one myself, heh).
> 
> Yeah, that's my big problem with anything IDE.    My personal experience of 
> failure rates for IDE drives, for example, is about 1 out of 10 fails in 
> service before it's a year old; SCSI has been more like 1 out of 50.  

Um. I'm pretty sure the actual hardware is just the same stuff. It's just the
interface electronics that change.

> Also, while I've seen benchmarks like Escalade's, my real-world experience has 
> been that the full bi-directional r/w of SCSI means that it takes 2 SATA 
> drives to equal one SCSI drive in a heavy r/w application.   However, ODSL is 
> all SCSI so I don't have any numbers to back that up.

Do we know that these SATA/IDE controllers and drives don't "lie" about fsync
the way most IDE drives do? Does the controller just automatically disable the
write caching entirely?

I don't recall, did someone have a program that tested the write latency of a
drive to test this?

-- 
greg




view thread (36+ messages)  latest in thread

Message-ID: <874qhjvoe1.fsf@stark.xeocode.com>
Permalink:  ../874qhjvoe1.fsf@stark.xeocode.com/
Also on:    postgresql.org/message-id/874qhjvoe1.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, josh@agliodbs.com, merlin.moncure@rcsonline.com, alex@neteconomist.com
  Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
  In-Reply-To: <874qhjvoe1.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