From: J. Andrew Rogers <jrogers@neopolitan.com>
To: Paul Tuckfield <paul@tuckfield.com>
To: pgsql-performance@postgresql.org
Subject: Re: Configuring PostgreSQL to minimize impact of
Date: 11 May 2004 15:32:41 -0700
Message-ID: <1084314760.4100.53.camel@localhost.localdomain> (raw)
In-Reply-To: <905B43ED-A395-11D8-A34F-000393BD6C3E@tuckfield.com>
References: <Pine.LNX.4.33.0405111417380.23073-100000@css120.ihs.com>
<905B43ED-A395-11D8-A34F-000393BD6C3E@tuckfield.com>
On Tue, 2004-05-11 at 14:52, Paul Tuckfield wrote:
> Love that froogle.
>
> It looks like a nice card. One thing I didn't get straight is if
> the cache is writethru or write back.
The LSI MegaRAID reading/writing/caching behavior is user configurable.
It will support both write-back and write-through, and IIRC, three
different algorithms for reading (none, read-ahead, adaptive). Plenty
of configuration options.
It is a pretty mature and feature complete hardware RAID implementation.
j. andrew rogers
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: jrogers@neopolitan.com, paul@tuckfield.com
Subject: Re: Configuring PostgreSQL to minimize impact of
In-Reply-To: <1084314760.4100.53.camel@localhost.localdomain>
* 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