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 65F4F3A4817 for ; Thu, 20 Jan 2005 16:06:05 +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 20380-03 for ; Thu, 20 Jan 2005 16:05:59 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by svr1.postgresql.org (Postfix) with ESMTP id 9E3103A4811 for ; Thu, 20 Jan 2005 16:05:58 +0000 (GMT) Received: by wproxy.gmail.com with SMTP id 50so149875wri for ; Thu, 20 Jan 2005 08:05:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BkbO1uW3BuMv9X73Z6FOd3CgC57NPUEpfVslsPs5GZD9RPvqJT5JXfUZcVXyR5SBu5cGwQdjI7A3DdG3BE9NKEwRfwPD3EgcUCgpD7i7iG/lL/5rBSLzPtTL3U6XoLuNQg8JhiAX8qKW9aBfQg/HFcEz1nirg2ECLOllBU63LBA= Received: by 10.54.30.15 with SMTP id d15mr135664wrd; Thu, 20 Jan 2005 08:05:57 -0800 (PST) Received: by 10.54.18.72 with HTTP; Thu, 20 Jan 2005 08:05:57 -0800 (PST) Message-ID: <33c6269f05012008054e094a4f@mail.gmail.com> Date: Thu, 20 Jan 2005 11:05:57 -0500 From: Alex Turner Reply-To: alex@neteconomist.com To: Benjamin Wragg Subject: Re: Disk configuration Cc: pgsql-performance@postgresql.org In-Reply-To: <20050120005537.AE5D08EAB6@vscan01.westnet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <33c6269f050119075217a42c42@mail.gmail.com> <20050120005537.AE5D08EAB6@vscan01.westnet.com.au> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200501/310 X-Sequence-Number: 10000 I have never seen benchmarks for RAID 0+1. Very few people use it because it's not very fault tolerant, so I couldn't answer for sure. I would imagine that RAID 0+1 could acheive better read throughput because you could, in theory, read from each half of the mirror independantly. Write would be the same I would imagine because you still have to write all data to all drives. Thats my best guess. Alex Turner NetEconomist On Thu, 20 Jan 2005 11:55:37 +1100, Benjamin Wragg wrote: > > Thanks. That sorts out all my questions regarding disk configuration. One > more regarding RAID. Is RAID 1+0 and 0+1 essentially the same at a > performance level? > > Thanks, > > Benjamin > -----Original Message----- > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org] On Behalf Of Alex Turner > Sent: Thursday, 20 January 2005 2:53 AM > To: Benjamin Wragg > Cc: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] Disk configuration > > The primary goal is to reduce the number of seeks a disk or array has to > perform. Serial write throughput is much higher than random write > throughput. If you are performing very high volume throughput on a server > that is doing multiple things, then it maybe advisable to have one partition > for OS, one for postgresql binaries, one for xlog and one for table data (or > multiple if you are PG8.0). This is the ultimate configuration, but most > people don't require this level of seperation. If you do need this level of > seperation, also bare in mind that table data writes are more likely to be > random writes so you want an array that can sustain a high levels of IO/sec, > so RAID 10 with 6 or more drives is ideal. If you want fault tolerance, > then RAID 1 for OS and postgresql binaries is a minimum, and I believe that > xlog can also go on a RAID 1 unless you need more MB/sec. Ultimately you > will need to benchmark any configuration you build in order to determine if > it's successfull and meets your needs. This of course sucks, because you > don't want to buy too much because it's a waste of $$s. > > What I can tell you is my own experience which is a database running with > xlog, software and OS on a RAID 1, with Data partition running on > 3 disk RAID 5 with a database of about 3 million rows total gets an insert > speed of about 200 rows/sec on an average size table using a compaq proliant > ML370 Dual Pentium 933 w/2G RAM. Most of the DB is in RAM, so read times > are very good with most queries returning sub second. > > Hope this helps at least a little > > Alex Turner > NetEconomist > > On Wed, 19 Jan 2005 09:03:44 +1100, Benjamin Wragg > wrote: > > > > I just wanted to bounce off the list the best way to configure disks > > for a postgresql server. My gut feeling is as follows: > > > > Keep the OS and postgresql install on seperate disks to the postgresql > > /data directory? > > Is a single hard disk drive acceptable for the OS and postgresql > > program, or will this create a bottle neck? Would a multi disk array > > be more appropriate? > > > > Cheers, > > > > Benjamin Wragg > > > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Anti-Virus. > > Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 17/01/2005 > > > > ---------------------------(end of broadcast)--------------------------- > TIP 4: Don't 'kill -9' the postmaster > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 17/01/2005 > > > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.300 / Virus Database: 265.7.1 - Release Date: 19/01/2005 > >