From: Greg Stark <gsstark@mit.edu>
To: jd@commandprompt.com
Cc: Greg Stark <gsstark@mit.edu>
Cc: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: alex@neteconomist.com
Cc: pgsql-performance@postgresql.org
Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
Date: 28 Mar 2005 16:36:06 -0500
Message-ID: <87wtrr1mih.fsf@stark.xeocode.com> (raw)
In-Reply-To: <1112043428.26232.43.camel@jd2.commandprompt.com>
References: <6EE64EF3AB31D5448D0007DD34EEB3412A75B4@Herge.rcsinc.local>
<8764zb353a.fsf@stark.xeocode.com>
<1112043428.26232.43.camel@jd2.commandprompt.com>
"Joshua D. Drake" <jd@commandprompt.com> writes:
> > I assume AMCC == 3ware now?
> >
> > Has anyone verified that fsync is safe on these controllers? Ie, that they
> > aren't caching writes and "lying" about the write completing like IDE
> > drives often do by default?
>
> The higher end AMCC/3ware controllers actually warn you about using
> write-cache. You have to explicitly turn it on within the controller
> bios.
Well that's a good sign.
But if they're using SATA drives my concern is that the drives themselves may
be doing some caching on their own. Has anyone verified that the controllers
are disabling the drive cache or issuing flushes or doing something else to be
sure to block the drives from caching writes?
--
greg
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, jd@commandprompt.com, merlin.moncure@rcsonline.com, alex@neteconomist.com
Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL?
In-Reply-To: <87wtrr1mih.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