X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 96480D1D272 for ; Tue, 11 May 2004 19:33:00 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 59263-08 for ; Tue, 11 May 2004 19:32:42 -0300 (ADT) Received: from mx1.neopolitan.us (mx1.neopolitan.us [65.87.16.224]) by svr1.postgresql.org (Postfix) with ESMTP id 5E66DD1B22A for ; Tue, 11 May 2004 19:32:38 -0300 (ADT) Received: from [65.87.16.98] (HELO [10.0.0.210]) by mx1.neopolitan.us (CommuniGate Pro SMTP 4.1.8) with ESMTP-TLS id 4213593; Tue, 11 May 2004 15:32:41 -0700 Subject: Re: Configuring PostgreSQL to minimize impact of From: "J. Andrew Rogers" To: Paul Tuckfield , pgsql-performance@postgresql.org In-Reply-To: <905B43ED-A395-11D8-A34F-000393BD6C3E@tuckfield.com> References: <905B43ED-A395-11D8-A34F-000393BD6C3E@tuckfield.com> Content-Type: text/plain Organization: Message-Id: <1084314760.4100.53.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 May 2004 15:32:41 -0700 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/98 X-Sequence-Number: 6929 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