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 9D26852828 for ; Sat, 18 Jun 2005 19:57:56 -0300 (ADT) 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 72542-01 for ; Sat, 18 Jun 2005 22:57:48 +0000 (GMT) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by svr1.postgresql.org (Postfix) with ESMTP id 484E7528CD for ; Sat, 18 Jun 2005 19:57:47 -0300 (ADT) Received: from osgiliath.mathom.us ([70.108.108.63]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IIA00HBUYGDDKZ8@vms046.mailsrvcs.net> for pgsql-performance@postgresql.org; Sat, 18 Jun 2005 17:57:50 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by osgiliath.mathom.us (Postfix) with ESMTP id 33108612797 for ; Sat, 18 Jun 2005 18:57:49 -0400 (EDT) Received: from osgiliath.mathom.us ([127.0.0.1]) by localhost (osgiliath [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03618-03 for ; Sat, 18 Jun 2005 18:57:49 -0400 (EDT) Received: by osgiliath.mathom.us (Postfix, from userid 1000) id 107B76031F9; Sat, 18 Jun 2005 18:57:49 -0400 (EDT) Date: Sat, 18 Jun 2005 18:57:49 -0400 From: Michael Stone Subject: Re: Fwd: Multiple disks: RAID 5 or PG Cluster In-reply-to: To: pgsql-performance@postgresql.org Mail-Followup-To: pgsql-performance@postgresql.org Message-id: <20050618225748.GI25854@mathom.us> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-disposition: inline X-Pgp-Fingerprint: 53 FF 38 00 E7 DD 0A 9C 84 52 84 C5 EE DF 7C 88 X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at mathom.us References: User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.035 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200506/359 X-Sequence-Number: 12996 On Sat, Jun 18, 2005 at 06:42:27PM +0200, Yves Vindevogel wrote: >>With striping, each file is distributed over several disks, making >>the physical write faster because several disks can do the work. >>Same for reading, multiple disks return a part of the file. A mirror behaves almost exactly the same for reads, with a caveat: for a large enough file, multiple disks *must* be accessed in a striped configuration, while in a mirrored configuration the controller may access either one or more disks to read any file. >>BTW: mirroring is always slower than striping. That's simply not true. Striping speeds up writes but has no advantage over a simlarly sized mirror for reading. In fact, the mirror will be faster for pathological cases in which the reads are aligned in such a way that they would all be have to be read from the same stripe of a striped array. The striped configuration has an advantage when more than two disks are used, but that derives from the number of spindles, not from the striping; it is possible to have a mirror of more than two disks (which would have the same read advantage as the striped configuration with the same number of disks) but this is rarely seen because it is expensive. Mike Stone