From: Ron Peacetree <rjpeace@earthlink.net>
To: Mark Lewis <mark.lewis@mir3.com>
To: Vivek Khera <vivek@khera.org>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: hardare config question
Date: Fri, 28 Apr 2006 14:19:23 -0400 (GMT-04:00)
Message-ID: <29786081.1146248363265.JavaMail.root@elwamui-royal.atl.sa.earthlink.net> (raw)
The best of all worlds is to use a HW RAID card with battery backed cache.
Then you can have both high performance and high reliability.
Benches suggest that the best such cards currently are the Areca cards which support up to 2GB of battery backed cache.
Ron
-----Original Message-----
>From: Mark Lewis <mark.lewis@mir3.com>
>Sent: Apr 28, 2006 1:47 PM
>To: Vivek Khera <vivek@khera.org>
>Cc: Pgsql performance <pgsql-performance@postgresql.org>
>Subject: Re: [PERFORM] hardare config question
>
>It's also possible that the single SATA drive you were testing (or the
>controller it was attached to) is lying about fsync and performing write
>caching behind your back, whereas your new controller and drives are
>not.
>
>You'll find a lot more info on the archives of this list about it, but
>basically if your application is committing a whole lot of small
>transactions, then it will run fast (but not safely) on a drive which
>lies about fsync, but slower on a better disk subsystem which doesn't
>lie about fsync.
>
>Try running a test with fsync=off with your new equipment and if it
>suddenly starts running faster, then you know that's the problem.
>You'll either have a choice of losing all of your data the next time the
>system shuts down uncleanly but being fast, or of running slow, or of
>fixing the applications to use chunkier transactions.
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: rjpeace@earthlink.net, mark.lewis@mir3.com, vivek@khera.org
Subject: Re: hardare config question
In-Reply-To: <29786081.1146248363265.JavaMail.root@elwamui-royal.atl.sa.earthlink.net>
* 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