From: Alex Turner <armtuk@gmail.com>
To: Pete de Zwart <dezwart@froob.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Best filesystem for PostgreSQL Database Cluster under Linux
Date: Fri, 14 Jan 2005 10:51:50 -0500
Message-ID: <33c6269f050114075179a035cf@mail.gmail.com> (raw)
In-Reply-To: <41e4364a$0$96874$c30e37c6@ken-reader.news.telstra.net>
References: <41e39b04$0$96857$c30e37c6@ken-reader.news.telstra.net>
<m3zmzgayzl.fsf@knuth.knuth.cbbrowne.com>
<41e4364a$0$96874$c30e37c6@ken-reader.news.telstra.net>
On Wed, 12 Jan 2005 07:25:43 +1100, Pete de Zwart <dezwart@froob.net> wrote:
[snip]
> improvement on I/O compared to the improvement potential of moving to
> SCSI/FCAL, that and getting more memory.
>
I would like to ask the question that continues to loom large over all
DBAs. SCSI, FCAL and SATA, which works best.
Most FCAL loops have a speed limit of either 1Gbps or 2Gbps. This is
only 100MB/sec or 200MB/sec. U320 SCSI can handle 320MB/sec and the
AMCC (formerly 3Ware) SATA Raid cards show throughput over 400MB/sec
with good IOs/sec on PCI-X.
I am not prepared to stand by whilst someone makes a sideways claim
that SCSI or FCAL is implicitly going to give better performance than
anything else. It will depend on your data set, and how you configure
your drives, and how good your controller is. We have a Compaq Smart
Array controler with a 3 drive RAID 5 than can't break 10MB/sec write
on a Bonnie++ benchmark. This is virtualy the slowest system in our
datacenter, but has a modern controler and 10k disks, whilst our PATA
systems manage much better throughput. (Yes I know that MB/sec is not
the only speed measure, it also does badly on IO/sec).
Alex Turner
NetEconomist
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, dezwart@froob.net
Subject: Re: Best filesystem for PostgreSQL Database Cluster under Linux
In-Reply-To: <33c6269f050114075179a035cf@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