From: Tom Lane <tgl@sss.pgh.pa.us>
To: adler@pobox.com
Cc: pgsql-performance@postgresql.org
Subject: Re: inferior SCSI performance
Date: Wed, 17 Sep 2003 15:08:33 -0400
Message-ID: <4693.1063825713@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.NEB.4.58.0309171445240.1444@reva.sixgirls.org>
References: <3F688CC5.12621.4EBFDCC@localhost>
<Pine.NEB.4.58.0309171445240.1444@reva.sixgirls.org>
Michael Adler <adler@pobox.com> writes:
> I have been experimenting with a new Seagate Cheetah 10k-RPM SCSI to
> compare with a cheaper Seagate Barracuda 7200-RPM IDE (each in a
> single-drive configuration). The Cheetah definately dominates the generic
> IO tests such as bonnie++, but fares poorly with pgbench (and other
> postgresql operations).
It's fairly common for ATA drives to be configured to lie about write
completion (ie, claim write-complete as soon as data is accepted into
their onboard RAM buffer), whereas SCSI drives usually report write
complete only when the data is actually down to disk. The performance
differential may thus be coming at the expense of reliability. If you
run Postgres with fsync off, does the differential go away?
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, adler@pobox.com
Subject: Re: inferior SCSI performance
In-Reply-To: <4693.1063825713@sss.pgh.pa.us>
References: <3F688CC5.12621.4EBFDCC@localhost> <Pine.NEB.4.58.0309171445240.1444@reva.sixgirls.org> <4693.1063825713@sss.pgh.pa.us>
* 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