X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E7C9656635 for ; Fri, 11 Mar 2005 08:06:03 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 32585-06 for ; Fri, 11 Mar 2005 08:06:02 +0000 (GMT) Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by svr1.postgresql.org (Postfix) with ESMTP id 0DFFE56601 for ; Fri, 11 Mar 2005 08:05:59 +0000 (GMT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-33.mail.demon.net with esmtp (Exim 4.42) id 1D9f9i-000MGM-C8; Fri, 11 Mar 2005 08:05:59 +0000 Received: from [192.168.1.17] (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id A990A166EC; Fri, 11 Mar 2005 08:05:57 +0000 (GMT) Message-ID: <42315165.1050202@archonet.com> Date: Fri, 11 Mar 2005 08:05:57 +0000 From: Richard Huxton User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karim Nassar Cc: John A Meinel , pgsql-performance@postgresql.org Subject: Re: What's better: Raid 0 or disk for seperate pg_xlog References: <1110440684.6368.163.camel@k2.cet.nau.edu> <4230673B.3020400@arbash-meinel.com> <1110484232.9252.211.camel@k2.cet.nau.edu> In-Reply-To: <1110484232.9252.211.camel@k2.cet.nau.edu> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.063 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200503/184 X-Sequence-Number: 10889 Karim Nassar wrote: > Thanks to all for the tips. > > On Thu, 2005-03-10 at 09:26 -0600, John A Meinel wrote: > >>How critical is your data? How update heavy versus read heavy, etc are you? > > > Large, relatively infrequent uploads, with frequent reads. The > application is a web front-end to scientific research data. The > scientists have their own copy of the data, so if something went really > bad, we could probably get them to upload again. If you have very few updates and your reads aren't mostly from RAM you could be better off with simply mirroring (assuming that gains you read bandwidth). Failing that, use the tablespace feature to balance your read load as far as you can. -- Richard Huxton Archonet Ltd