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 762D4533A7 for ; Mon, 18 Apr 2005 12:17:30 -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 47908-04 for ; Mon, 18 Apr 2005 15:17:27 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by svr1.postgresql.org (Postfix) with ESMTP id D94A55336D for ; Mon, 18 Apr 2005 12:17:26 -0300 (ADT) Received: by wproxy.gmail.com with SMTP id 68so1488928wri for ; Mon, 18 Apr 2005 08:17:25 -0700 (PDT) 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:content-disposition:references; b=m/UwFCkYLCo9YojbU/l06uvIXXi6BgewuzEyNCx1kp5r1oELevhaov15y5uOrh5w5zcU4KvX07+MlW6uc4ZSKZq6CNYQaPw1iHKIQ/Oy1F2raPxSROT0ZIgtBwX/XDYz3krJ5MCT6DVUcXwS8UdUMIPseGN0uTrEUWzZu4+6Oe0= Received: by 10.54.31.32 with SMTP id e32mr3367668wre; Mon, 18 Apr 2005 08:17:25 -0700 (PDT) Received: by 10.54.86.16 with HTTP; Mon, 18 Apr 2005 08:17:25 -0700 (PDT) Message-ID: <33c6269f0504180817511b27a3@mail.gmail.com> Date: Mon, 18 Apr 2005 11:17:25 -0400 From: Alex Turner Reply-To: Alex Turner To: Greg Stark Subject: Re: How to improve db performance with $7K? Cc: William Yu , pgsql-performance@postgresql.org In-Reply-To: <87pswsku6e.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <425EBA0C.6030804@sfnet.cc> <87pswsku6e.fsf@stark.xeocode.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.275 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, RCVD_BY_IP X-Spam-Level: X-Archive-Number: 200504/400 X-Sequence-Number: 11797 This is fundamentaly untrue. A mirror is still a mirror. At most in a RAID 10 you can have two simultaneous seeks. You are always going to be limited by the seek time of your drives. It's a stripe, so you have to read from all members of the stripe to get data, requiring all drives to seek.=20 There is no advantage to seek time in adding more drives. By adding more drives you can increase throughput, but the max throughput of the PCI-X bus isn't that high (I think around 400MB/sec) You can easily get this with a six or seven drive RAID 5, or a ten drive RAID 10. At that point you start having to factor in the cost of a bigger chassis to hold more drives, which can be big bucks. Alex Turner netEconomist On 18 Apr 2005 10:59:05 -0400, Greg Stark wrote: >=20 > William Yu writes: >=20 > > Using the above prices for a fixed budget for RAID-10, you could get: > > > > SATA 7200 -- 680MB per $1000 > > SATA 10K -- 200MB per $1000 > > SCSI 10K -- 125MB per $1000 >=20 > What a lot of these analyses miss is that cheaper =3D=3D faster because c= heaper > means you can buy more spindles for the same price. I'm assuming you pick= ed > equal sized drives to compare so that 200MB/$1000 for SATA is almost twic= e as > many spindles as the 125MB/$1000. That means it would have almost double = the > bandwidth. And the 7200 RPM case would have more than 5x the bandwidth. >=20 > While 10k RPM drives have lower seek times, and SCSI drives have a natura= l > seek time advantage, under load a RAID array with fewer spindles will sta= rt > hitting contention sooner which results into higher latency. If the contr= oller > works well the larger SATA arrays above should be able to maintain their > mediocre latency much better under load than the SCSI array with fewer dr= ives > would maintain its low latency response time despite its drives' lower av= erage > seek time. >=20 > -- > greg >=20 >=20 > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if you= r > joining column's datatypes do not match >